comfy-image-mcp

Overview Schema Source Related Servers Discussions Admin

Check the image backend

image_backend_status

Checks ComfyUI connectivity and reports GPU/VRAM, configured workflows, and image output root so you can verify the backend before generating; it creates no images.

Instructions

Reports whether ComfyUI is reachable, GPU/VRAM, which workflows (txt2img, edit, cutout) are configured, and the project root images are written to. Does not generate anything.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is purely diagnostic and has no side effects, and it names the categories of information surfaced. It stops short of noting error behavior (e.g. what happens if ComfyUI is down) or that results are a snapshot rather than a live probe.

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 dense sentence that front-loads the core answer (reachability) before the supplementary details, plus one short exclusion clause. Nothing is redundant and no sentence is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Absent an output schema, the description must convey what comes back, and it enumerates all four return categories including the project root path. Combined with the explicit non-mutation statement, an agent has everything needed to call it and interpret the result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly implies a parameterless check by describing a fixed status report.

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?

Uses a specific verb ('Reports whether ComfyUI is reachable') and enumerates the exact facts returned: reachability, GPU/VRAM, configured workflows, and the image output root. It also carves out the boundary against the sibling by stating 'Does not generate anything', so an agent can distinguish it from generate_image without inspecting either schema.

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?

The negative clause 'Does not generate anything' implicitly identifies this as the diagnostic/read counterpart to generate_image, which is clear context for selection. However, it never states the positive trigger ('call before generating' or 'call when generation fails'), leaving the when-to-use inference to the agent.

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

Deploy Server