Tool Combine

LLM Party's agent nodes don't take a scattered handful of tool wires - they expect one combined tools input. tool_combine is the junction node that gets you there: plug in up to three of the pack's tool-producing nodes (time_tool, sql_tool, url2img_tool, story_json_tool, or any others from this pack's tool family you're using - the README also mentions built-in web search, weather, and code-interpreter tools), and it merges them into a single bundle your LLM/agent node can actually consume.

This is deliberately the simple version. All three slots are optional, so you're not forced to fill every one - plug in one tool and leave the rest empty, and it still works.

Inputs and outputs that matter

• tool1, tool2, tool3 - each optional, each expecting the tool output from one of this pack's tool nodes.
• is_enable - the pack-wide skip switch.

The single output, tools, is the merged bundle - wire it into your LLM/agent node's tool input, or into another tool_combine/tool_combine_plus if you're layering combinations.

Installing it

Search comfyui_LLM_party in ComfyUI Manager and install, or clone directly:

cd ComfyUI/custom_nodes
git clone https://github.com/heshengtao/comfyui_LLM_party

pip install -r requirements.txt inside your ComfyUI Python environment, then restart. This node itself is pure plumbing - no model or API dependency - but it's bundled inside the full pack, which is a much larger install overall. If you only need API-based LLM calling, the README's only_api branch is the lighter path.

Common issues

The main thing to know about tool_combine is when to stop using it: three slots is a hard ceiling. If your agent needs a fourth tool, this node genuinely can't take it - you either chain a second tool_combine (feeding one's tools output into an empty slot of another, if the socket types line up for that) or switch to tool_combine_plus, which offers ten slots from the start. For anything beyond a very small, fixed toolset, it's usually simpler to just start with tool_combine_plus rather than outgrowing this one mid-build.

Otherwise, since this is a merge step and not a tool itself, an empty or misconfigured slot generally just means one fewer capability for the agent - it won't be the thing that throws an error if, say, sql_tool's database connection is broken. If a tool your agent should have access to doesn't seem to be working, check that individual tool node's own configuration first; tool_combine is rarely where the actual problem lives.

It's also worth being intentional about which tools you actually combine, rather than wiring in everything the pack offers "just in case." Every tool you add is one more thing the model has to weigh when it's deciding what to do next, and a cluttered toolset can make an agent worse at picking the right tool at the right moment, not better. Three slots is a reasonable natural limit for a focused agent - treat outgrowing it as a signal to think about scope, not just a reason to reach for tool_combine_plus.