Griptape Combine: Tool List

A Griptape agent with no tools is just a chatbox. Give it tools and it can calculate, look things up, scrape websites, manage files, query a knowledge base. Griptape Combine: Tool List is the node that bundles all of those separate tool outputs into one TOOL_LIST you can drop onto an agent. Without it, wiring three tools to an agent means either multiple connections or hand-editing - with it, it's one clean wire.

What it's for

The pack ships tool nodes like Calculator, DateTime, WebScraper, FileManager, and Knowledge Base / Vector Store tools. Each one outputs a TOOL_LIST with a single tool inside. Combine Tool List takes those one-tool lists and flattens them into a single list with all of them. That combined list is exactly what Griptape Create: Agent expects on its tools input.

The README's framing is "Give Agents access to Tools," and this is the merge step that makes a multi-tool agent a one-connection affair instead of a spaghetti of wires.

How it works

Same pattern as every combine node in the pack:

tool_list = []
for tool in tools:
    tool_list.append(tool[0])

Each connected input contributes its first tool, and they're collected in order. No dedup, no filtering - if you connect the same tool twice, the agent gets it twice (which is mostly harmless, but pointless).

Inputs and output

• tool_1 (TOOL_LIST) - a tool output to add. Connect more tool nodes and more inputs appear dynamically.
• Output: TOOL_LIST - the combined set, wired into an agent's tools input.

You can also chain these: Combine Tool List into another Combine Tool List, if you're assembling tools from several branches of a workflow. It's just list flattening, so nesting works fine.

Installation

Part of ComfyUI Griptape Nodes:

• ComfyUI Manager: search "Griptape" → install.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/griptape-ai/ComfyUI-Griptape, restart ComfyUI.

Same shared install as the rest of the pack - griptape[all], python-dotenv, openai - and the README's torch troubleshooting if the environment gets cranky.

Gotchas

• This is pure assembly, no logic and no LLM involvement. If your agent isn't using a tool, the problem is usually the agent config (missing API key for that tool, or the tool needing a driver), not this node.
• Keep an eye on what each tool node needs. WebScraper and the cloud tools often require their own API keys or drivers before they'll actually function - combining them doesn't magically configure them.

One wire in, whole toolbox out. It's the node that makes "agent that can do more than chat" a one-connection build.