Skip to main content
Glama

save_workflow

Saves a ComfyUI API workflow under a name so run_workflow can reuse it, then returns its inputs.

Instructions

Keeps a workflow (ComfyUI API format) under a name, so run_workflow can use it. Returns its inputs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "workflow": "<workflow>"
    },
    "name": "save_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
workflowYes
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false with destructiveHint=false, so the agent knows a non-destructive write occurs; the description adds that the call returns the workflow's inputs. However, it does not disclose persistence lifetime, whether saving an existing name fails or silently replaces, or whether name collisions are rejected — all material for a storage mutation.

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?

Two short sentences with the purpose front-loaded and the return behavior appended; nothing is filler. It is a bit too terse for the ambiguities it leaves unresolved, but no sentence is wasted.

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?

There is no output schema, and the one-line "Returns its inputs" only partially covers the return value. For a stateful save operation with a nested free-form `workflow` object and an overwrite flag, the definition is thin on collision behavior, storage scope, and validation requirements.

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%, so the description carries the full burden. It clarifies the `name` semantics and adds a useful format constraint on `workflow` (ComfyUI API format), but the `overwrite` boolean — the parameter with the most consequential behavior — is never mentioned, leaving its semantics 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?

States a specific verb and resource ("Keeps a workflow ... under a name") plus the format (ComfyUI API format) and its downstream consumer (run_workflow), which separates it from run_workflow itself. It does not differentiate from check_workflow or any other sibling, leaving a small ambiguity.

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 description implies the usage context by naming run_workflow as the consumer, so an agent can infer this is a prerequisite registration step. It gives no explicit when-to-use vs when-not guidance, and says nothing about when to pass overwrite or what happens if the name already exists.

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