Skip to main content
Glama

list_models

Discover available ComfyUI models—UNet, CLIP, VAE, and LoRA—to choose compatible assets for workflow generation. Filter by model type when planning or validating a ComfyUI workflow.

Instructions

Discover available models: unet, clip, vae, lora

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_typeNoall

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that the result is a set of available models grouped by type, and 'Discover' implies a non-mutating read. It says nothing about permissions, cost, or failure modes, though the presence of an output schema removes the need to describe the return payload in detail.

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?

A single front-loaded sentence with no filler. It is perhaps too terse, but every word is doing work and nothing is redundant.

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 one-parameter read-only listing tool with an output schema, the description covers what is enumerated. It leaves the model_type filter's behavior and the intended workflow (list, then download) unexplained, which is a moderate gap rather than a fatal one.

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% for the single model_type parameter, so the description must compensate. It partially does by naming the four model categories, which are the likely filter values, but it never states that model_type selects among these categories or how it interacts with the 'all' default.

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?

Uses the verb 'Discover' with the resource 'models' and enumerates the four categories (unet, clip, vae, lora), so an agent knows it is an enumeration tool, not a loader. It does not name or contrast itself with the obvious sibling download_model, so the sibling differentiation is left implicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as download_model or get_comfyui_status. At best the word 'Discover' hints that this is a lookup step, but nothing states when it should be preferred over another tool.

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