Skip to main content
Glama

download_model

Downloads a selected model and its helper files for local ComfyUI use; for large files, reports size and requires user_confirmed=true to proceed.

Instructions

Downloads a model from our list (ids from list_models), with any helper files it needs. Big downloads: tell the user the size and call again with user_confirmed=true.

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": {
      "model_id": "<model_id>"
    },
    "name": "download_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes
user_confirmedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive operation, so the safety profile is partly covered. The description adds genuinely new behavior: helper files are fetched alongside the model, and large downloads require a second confirmed call. It still omits where files land, whether existing files are overwritten, and what threshold counts as "big".

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?

Two short sentences, no filler, with the prerequisite and the confirmation workflow both front-loaded. Every clause carries actionable information.

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 2-parameter mutation with no output schema and no descriptions on the schema itself, the definition covers the call flow but not the outcome — an agent does not learn what comes back (e.g., a job id it should poll with download_status) or where the files are written. Adequate to invoke, incomplete for driving the follow-up.

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 parameters, and it does explain both: model_id is sourced from list_models, and user_confirmed is the re-call flag for large downloads. It does not say what qualifies as large or what happens if user_confirmed is set on a small model.

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

Purpose4/5

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

Specific verb+resource ("Downloads a model") with scope clarified as coming from the list exposed by list_models, and it notes that helper files come along. It stops short of tying itself to the related lifecycle tools (cancel_download, download_status), but the purpose is unambiguous.

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?

Gives a concrete prerequisite (model ids come from list_models) and a conditional usage rule: for big downloads, report size to the user and re-call with user_confirmed=true. That is real when-to-use guidance; only the absence of explicit when-not/exclusion guidance keeps it from a 5.

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