Skip to main content
Glama

comfyui_status

Read-only

Check whether ComfyUI is running, which GPU and memory it uses, free disk space, and what is currently rendering before you start a video job.

Instructions

Is ComfyUI running, which graphics card and how much memory it has, free disk space, and what is rendering.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds useful content disclosure — it tells the agent this returns hardware, disk, and live render information — but says nothing about behavior when ComfyUI is down, whether it blocks, or latency.

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 compact sentence that front-loads the primary question ('Is ComfyUI running') and then lists the secondary payload. Every clause adds a distinct return field; there is no filler, though the comma-list style is slightly run-on.

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 parameters and no output schema, the description carries the burden of describing returns and does so by enumerating the five data points an agent would get back. Only the failure/offline behavior is left unstated, a minor gap for a simple read-only status probe.

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 no parameter meaning to convey; the baseline for a no-param tool applies. Nothing in the description misrepresents or over-specifies the empty input contract.

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 the resource (ComfyUI) and enumerates exactly what status it reports: running state, GPU model, memory, free disk space, and current render activity. That is specific enough to distinguish it from generic job/download status tools, though it never explicitly contrasts itself with job_status or free_gpu_memory.

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?

The interrogative phrasing ('Is ComfyUI running...') implies the health-check use case but never states when to call it versus job_status or free_gpu_memory, nor any preconditions. Usage is inferred rather than guided.

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