Skip to main content
Glama

status

Check whether the local ComfyUI backend is running or managed by localgen, along with idle timeout bounds, queue length, GPU memory, and installed workflow model files.

Instructions

Backend state: running or not, managed by localgen or not, effective idle timeout and bounds, queue length, GPU memory, and which workflows have their model files installed.

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": "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?

With no annotations, the description must carry the full behavioral burden. It does well at disclosing the exact information returned (timeout bounds, queue length, GPU memory, installed models), but it never states whether the call is side-effect free, whether querying state can itself spin up the backend, or whether it is cheap to poll.

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 dense sentence that front-loads 'Backend state' and then lists the returned facets. Every listed item is a distinct field an agent would want, so nothing is filler, though the list could be tightened slightly.

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?

For a zero-parameter read tool with no annotations and no output schema, the description effectively substitutes for the missing output schema by enumerating the returned fields. The remaining gap is the absence of any statement about side effects or cost of polling.

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 of 4 applies. The description adds no spurious parameter discussion, which is appropriate.

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 enumerates exactly what the tool reports: backend running state, whether it is managed by localgen, idle timeout and bounds, queue length, GPU memory, and installed model files per workflow. That is a precise resource and scope, clearly distinct from the sibling start_backend/stop_backend mutations, though the verb ('report') is left implicit by the bare name 'status'.

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 only implied: an agent can infer this is the diagnostic call to make before or instead of start_backend/stop_backend, but the description never says when to call it or names an alternative. No exclusions or preconditions are stated.

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