Skip to main content
Glama

check_model

Determines if a local or Hugging Face model file can run in ComfyUI and explains why it cannot, without loading the model.

Instructions

Says if a model file can run here and why not if it can't, without loading it. A file on this PC: file="C:/path/model.gguf" or a file name in ComfyUI's models folder. A file on Hugging Face (from search_models): repo="owner/name" and file="path/in/repo.gguf".

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": "check_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
repoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, so network access is signalled structurally; the description reinforces it by tying repo= to Hugging Face and adds the non-obvious fact that the model is not loaded. However it does not say whether the HF metadata is fetched over the network, how large/expensive that fetch is, or what the verdict text looks like — notable gaps given readOnlyHint=false hints at side effects (e.g. caching) that are never explained.

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 short lines, front-loaded with the purpose and then the two supported argument shapes; every clause carries information an agent needs to form a correct call.

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?

No output schema exists, yet the description conveys the return semantics ('says if it can run here and why not'), which is the essential part for a two-parameter check tool. Completeness is only slightly reduced by the unexplained cost/behavior of the Hugging Face branch and the undefined both-arguments-empty case.

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 coverage is 0%, so the description must carry the parameter burden, and it largely does: file is either an absolute path or a bare name resolved in ComfyUI's models folder, and repo/file combine for HF sources with example syntax. It omits that both parameters are optional and what an empty call means, leaving one real ambiguity.

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?

Names a specific verb and object — reporting whether a model file can run on this machine, and why not when it can't — plus a distinguishing scope clause ('without loading it'). An agent can immediately tell this apart from search_models, which the description explicitly positions as the upstream source of repo ids.

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 concrete usage forms for the two cases (local file path or ComfyUI models-folder name; Hugging Face repo plus in-repo path) and ties the repo case to search_models output. It stops short of stating exclusions, e.g. what happens if neither argument is supplied or when to skip the check.

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