Skip to main content
Glama

start_comfyui

Launches ComfyUI with VRAM-optimized flags such as FP16 and low-VRAM mode, helping agents run workflows on GPUs with limited memory.

Instructions

Launch ComfyUI with VRAM-optimized flags

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
fp16No
portNo
lowvramNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses almost nothing. It does not say whether the launch is blocking, how long startup takes, what happens if ComfyUI is already running, whether the port must be free, or the fact that defaults enable low-VRAM behavior. "VRAM-optimized flags" is the only behavioral hint.

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 front-loaded sentence with zero filler — the core action lands immediately. It is efficient, though the brevity edges toward under-specification rather than true conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, but for a process-launch tool with three undocumented parameters and no annotations, the description omits the lifecycle and failure context an agent needs to invoke it safely. It is well short of complete for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, so the description must compensate. The phrase "VRAM-optimized flags" loosely points at lowvram and fp16, but nothing explains what fp16 actually toggles, what port is for, or the consequences of changing defaults. Port is left entirely undocumented.

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?

"Launch ComfyUI" is a specific verb+resource pair, and "with VRAM-optimized flags" adds the distinguishing detail that separates it from stop_comfyui and get_comfyui_status in the sibling set. It never names those siblings or states the contrast explicitly, so it stops short of full differentiation.

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?

The description gives no when-to-use guidance, no prerequisites (e.g. whether ComfyUI must be stopped first, whether a port conflict is possible), and no alternatives. An agent must infer entirely from the verb that this is the start step of a lifecycle.

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