Skip to main content
Glama

install_custom_node

Installs ComfyUI node packs from a GitHub link, pack name, or detected node type. Requires user confirmation and a ComfyUI restart afterward.

Instructions

Installs a ComfyUI node pack: a GitHub link, a pack name, or a node type from check_workflow. Node packs are programs from other people, so ASK THE USER FIRST, then call again with user_confirmed=true. ComfyUI needs a restart after (restart_comfyui).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>"
    },
    "name": "install_custom_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
user_confirmedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=false, openWorldHint=true and destructiveHint=false. The description adds material context beyond that: node packs are third-party programs (a supply-chain risk), a mandatory human consent gate tied to user_confirmed, and a required restart afterward. No contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: capability, safety/consent protocol, then post-condition. The risk warning and the required action are front-loaded and nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, it covers what an agent needs to act safely: accepted inputs, consent requirement, and restart follow-up. It omits failure/long-running behavior and any indication of what a successful call returns, minor gaps given no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load and largely does: it defines what `source` can be (GitHub link, pack name, or node type) and explains the purpose of `user_confirmed` through the ask-then-confirm flow. It stops short of stating exact expected formats or matching behavior for pack names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'Installs a ComfyUI node pack.' It then enumerates the three accepted source forms (GitHub link, pack name, node type from check_workflow), which distinguishes it from sibling tools like download_model or add_model_file that also fetch external artifacts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit two-step protocol — ask the user first, then re-call with user_confirmed=true — and names check_workflow as the source for node types plus restart_comfyui as the required follow-up. When-to-use, sequencing, and named alternatives are all present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.