Skip to main content
Glama

add_model_file

Registers an existing local model file by path for ComfyUI rendering, checking it first and linking without copying. After adding it, render calls can use the model by file name.

Instructions

Adds a model file that is already on this PC, where it is (a link, no copy). It is checked first. After this, render(model=) uses it.

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": {
      "path": "<path>"
    },
    "name": "add_model_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the file is linked rather than copied, and it is checked first. It does not explain what the check validates or what errors occur, but the key non-copy registration behavior is communicated.

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

Conciseness4/5

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

The description is short and front-loads the action and key constraint. The phrase 'It is checked first' is slightly vague, but overall it uses space efficiently with no unnecessary detail.

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

Completeness3/5

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

For a simple two-parameter local registration tool, it covers the main workflow and non-copy behavior. It still leaves the optional name parameter and validation failure behavior unclear, so it is adequate but not complete.

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

Parameters3/5

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

Schema description coverage is 0%, and the description clarifies the required path as the location of an existing file. However, the optional name parameter is only indirectly referenced as 'the file name' in the render example, leaving its default and aliasing behavior ambiguous.

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?

The description states a specific verb and resource: adding a model file already present on the PC. It also distinguishes this from copying or downloading by specifying 'a link, no copy' and gives the downstream render(model=...) usage.

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

Usage Guidelines4/5

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

It clearly indicates the tool is for local files that already exist and explains the follow-on render step. It does not explicitly name download_model as the alternative for remote models, but the local-file condition provides clear usage context.

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