Skip to main content
Glama

start_comfyui

Starts ComfyUI when it is not already running, taking 20-60 seconds, and does nothing if it is active. Use it to launch the local ComfyUI backend before rendering AI video clips.

Instructions

Starts ComfyUI if it is not running (takes 20-60 s). Does nothing if it already runs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world behavior. The description adds two things they do not: an expected duration of 20-60 s and no-op semantics when the service is already up, both of which matter for planning and retry decisions. It says nothing about failure modes or whether a timeout is possible.

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?

Two short sentences, the primary action is front-loaded, and the qualifier follows immediately. No waste.

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 lifecycle tool with no output schema, the description covers the essential facts: what it does, how long it takes, and that it is idempotent. The remaining gap is not pointing at restart_comfyui when a running instance needs replacing.

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 the baseline is 4. There is nothing for the description to clarify or omit on this dimension.

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?

"Starts ComfyUI if it is not running" names a specific verb and resource, and the idempotency clause distinguishes it implicitly from a restart-style sibling. It stops short of explicitly naming restart_comfyui, so an agent still has to infer which one to pick when the server is already up.

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 "does nothing if it already runs" clause gives a usable condition, but there is no explicit routing guidance to the sibling restart_comfyui when a running process should be recycled. Usage is implied rather than stated.

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