Skip to main content
Glama

stop_comfyui

Gracefully shuts down a running ComfyUI server, with an optional force flag to terminate it when a normal stop is not enough.

Instructions

Graceful shutdown of ComfyUI server

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

Input Schema

NameRequiredDescriptionDefault
forceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of disclosing behavior and it largely falls short. 'Graceful' implies in-flight work is allowed to finish, but the description never states what happens to actively running jobs, what distinguishes the force parameter, or whether the operation can be interrupted or undone. For a shutdown tool with zero annotation coverage, that is a substantial omission.

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?

One short, front-loaded phrase with no filler or redundancy. It is efficient, though its brevity is achieved by omitting rather than by disciplined selection of the most useful information.

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?

Because an output schema exists, the description need not explain return values, and the core action is stated. However, for a destructive lifecycle operation with no annotations, the absence of any note on the force parameter or on how running jobs are treated leaves a real gap for an agent deciding whether it is safe to 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 'force' (default false) is never mentioned in the description. The meaning of the graceful-versus-forced distinction, which is exactly what the parameter controls, is undocumented in both places, so the description does nothing to compensate for the schema gap.

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 pairs a specific verb ('Graceful shutdown') with a specific resource ('ComfyUI server'), so an agent can immediately tell this stops the server rather than restarting or querying it. It does not explicitly name start_comfyui or get_comfyui_status as the contrasting siblings, but the resource and action are unambiguous on their own.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives such as emergency_cleanup, nor any precondition (for example, whether the server must be running or whether jobs must be idle first). The word 'Graceful' hints at the intent but gives no conditions or exclusions.

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