Skip to main content
Glama

diagnose_job

Read-only

Explains why a ComfyUI job failed in plain language, suggests fixes to try, and includes relevant log lines for troubleshooting.

Instructions

Why a job failed, in plain words, with what to try and the ComfyUI log lines.

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": {
      "id": "<id>"
    },
    "name": "diagnose_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds valuable return-content context (plain-language diagnosis, suggested fixes, embedded ComfyUI log lines), but says nothing about edge cases such as a job that succeeded, a job that was not found, or whether logs are truncated.

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?

One tight, front-loaded clause of roughly fifteen words with zero filler. Every element, cause, remedy and log lines, tells the agent something about what comes back.

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 one-parameter read-only tool the description is mostly sufficient, and with no output schema it does sketch the return payload. It still leaves gaps around failure modes and result limits, and the unmatched parameter gives the agent little help before the call.

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

Parameters2/5

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

Schema description coverage is 0%, and the single parameter 'id' is never mentioned in the description. The name makes its meaning fairly obvious, but the description does nothing to compensate for the missing schema documentation, such as what kind of id it is and whether it is a job id or a prompt id.

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 states a specific outcome, explaining why a job failed, and what it returns: plain-language reasoning, remediation steps, and ComfyUI log lines. It distinguishes itself from job_status only implicitly (that one reports status, this one explains failure), so it stops short of 5.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'why a job failed', so the trigger is clear: reach for it after a failure. It names no exclusions or alternatives, though, such as get_logs for raw output or job_status for current state, leaving the agent to infer the boundary.

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