Skip to main content
Glama

restart_comfyui

Destructive

Restart ComfyUI to recover from a stuck state by stopping and starting it; the action is refused during video rendering and requires user confirmation.

Instructions

Stops and starts ComfyUI again. Fixes a stuck ComfyUI. Refused while a video renders. Ask the user first, then call with user_confirmed=true.

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

Input Schema

NameRequiredDescriptionDefault
user_confirmedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add context — and it does: it discloses a runtime guard ("Refused while a video renders") and a confirmation protocol. It stops short of saying what happens to other in-flight work or how long the restart takes, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the action and its purpose, then the guard, then the required confirmation step. Nothing is redundant and the call sequence is unambiguous.

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 single-parameter destructive tool with no output schema, this covers purpose, guard condition, and confirmation workflow adequately. The remaining gap is outcome detail — what the caller should expect on refusal or on success — which is minor given the annotation coverage.

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?

Schema coverage is 0%, so the description must carry the parameter, and it does explain that user_confirmed should be set true only after asking the user. It does not state what happens if it is left false, though "Refused" implies the call fails.

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?

"Stops and starts ComfyUI again" gives a specific verb pair and the exact resource, and the word "again" distinguishes it from a cold start. It does not explicitly name start_comfyui or comfyui_status as the alternatives, so the sibling differentiation is implied rather than stated.

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 description states the trigger condition ("Fixes a stuck ComfyUI") and an explicit precondition ("Ask the user first"), which is actionable guidance. It omits any statement about when a plain start or a status check would be the better choice.

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