Skip to main content
Glama

check_workflow

Read-only

Validate a saved or supplied ComfyUI workflow before a slow run by detecting missing node types, node packs, model files, wrong values, and listing changeable inputs.

Instructions

Before a slow run: finds missing node types (and which node pack has them), missing model files and wrong values in a saved workflow (name) or one you give (workflow, API format). Also lists its changeable inputs.

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_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
workflowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, and closed-world, and the description adds real substance beyond that: it reports which node pack supplies missing types and lists changeable inputs, which are output-side behaviors the annotations cannot convey. It does not explain whether a check has side effects on the saved workflow file, but for a read-only hint that gap is minor.

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?

A single tightly packed sentence with the trigger condition ('Before a slow run') front-loaded, followed by what it checks and which parameter carries which input. No filler, and the parentheticals are used for genuine clarification rather than restating schema.

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?

With no output schema, the description has to convey what comes back, and it does at a summary level: missing node types with their pack, missing model files, bad values, and changeable inputs. The main omission is whether it validates and reports only or can modify the workflow, and how conflicts between the two params are resolved.

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 load, and it does: it explains that 'name' refers to a saved workflow and 'workflow' is a workflow passed inline in API format. What it does not resolve is precedence when both are supplied or whether the object expects the API-format schema explicitly in the param.

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?

The description names a concrete verb-and-resource set: it finds missing node types, missing model files, and wrong values in a workflow. The 'before a slow run' framing distinguishes it as a preflight check rather than a runner, though it never names run_workflow directly.

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?

'Before a slow run' gives clear timing guidance that maps to a preflight-check use case, and the 'saved workflow (name) or one you give (workflow)' phrasing clarifies the two input modes. It stops short of explicit exclusions or naming the alternative tool it should precede.

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