Large Tool Combine

Same job as tool_combine, more room: instead of three optional tool slots, tool_combine_plus gives you ten (tool1 through tool10). It exists in this pack specifically because three genuinely isn't enough once an agent starts doing real work - an assistant that can query a database (sql_tool), check the time (time_tool), fetch an image from a link (url2img_tool), pull from a story knowledge base (story_json_tool), plus whatever else the pack offers for web search or code execution, blows past three slots fast.

Functionally it's identical to its smaller sibling - it just merges whatever's plugged into it into one combined tools output for your LLM/agent node to consume.

Inputs and outputs that matter

• tool1 through tool10 - ten optional slots, each expecting a tool output from one of this pack's tool-producing nodes. Fill as many or as few as you need.
• is_enable - the pack-wide skip switch.

The single output, tools, is the merged bundle, ready to feed into your agent node's tools input.

Installing it

Search comfyui_LLM_party in ComfyUI Manager and install, or clone by hand:

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. Like tool_combine, this node has no model or API dependency of its own - it's a merge step - but it's bundled with the rest of this large pack. The README's only_api branch is the lighter install if you only need API-based LLM calling.

Common issues

If you already know your agent is going to carry a real toolbox - more than two or three capabilities - just start with tool_combine_plus instead of the smaller tool_combine. Outgrowing three slots mid-build and having to rewire everything into a bigger combine node is a purely avoidable annoyance.

Beyond that, the same debugging rule applies as with tool_combine: this node merges, it doesn't validate. If one of your ten tools is broken - bad credentials on sql_tool, a database that isn't reachable, whatever - tool_combine_plus won't be the thing that surfaces the error. Go check the individual tool node first. And with ten tools available to a single agent, it's worth being deliberate in your system prompt about when each one should actually be used - more tools available doesn't automatically mean the model picks the right one at the right moment; that still comes down to how clearly you've described each tool's purpose.

There's also a real cost to just filling all ten slots because you can. Every additional tool is more surface area for the model to consider, and more room for it to reach for the wrong one, or invoke something it didn't need to. Ten slots is a ceiling, not a target - build the toolset your agent actually needs for its job, and leave the rest empty rather than treating an unused slot as wasted potential.