Story JSON Tool

Most of LLM Party's "tool" nodes - time_tool, url2img_tool, sql_tool - output a single capability under a socket literally named tool. story_json_tool is the odd one out: its output is called tools, plural, same as what you get from tool_combine. That's the tell for what this node actually is - it doesn't wrap one function, it loads a whole bundle of them at once, straight from a JSON file.

The path field is a dropdown of JSON files rather than a free-text field, and the sample choices on the node - one literally named story.json - point at what these files hold: structured story or scenario data, the kind of thing you'd use to give a role-play agent a consistent world, cast of characters, and rules to draw on, packaged as a set of callable tools rather than one giant prompt. That fits squarely with the README's pitch about building your "own exclusive AI assistant" and attaching personas - this is the piece that lets a role-play or interactive-fiction agent look things up from a defined story instead of improvising the lore from scratch every turn.

Inputs and outputs that matter

• path - pick which JSON file to load, from whatever's present in the node's expected folder. Defaults to story.json.
• is_enable - the pack-wide skip switch.

The output, tools, is a ready-made bundle - wire it straight into tool_combine / tool_combine_plus alongside any other tool nodes you're using, or directly into an agent node's tools input if that's the only source you need.

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 environment, then restart. This node itself doesn't need a model or API key - it's reading a local file - but it's bundled inside the full pack, which is large; if you only want the API-calling nodes and not local model support, the README documents a slimmer only_api branch.

Common issues

The path dropdown only shows files that are actually present - if you're expecting to use your own story data and it's not showing up as a choice, the file needs to be dropped into wherever this node looks for it (alongside the pack's other bundled JSON examples) before ComfyUI starts, not added while it's already running; custom node folders generally aren't re-scanned live.

Beyond that, treat this the same as feeding any structured data to an LLM tool: the JSON's shape matters. If you're authoring your own story file rather than using the bundled example, keep its structure consistent with what the node expects (look at the shipped story.json as the reference format) - a malformed or differently-shaped JSON file is far more likely to produce a confused agent than an outright crash, since the tool will still "load" successfully either way.