Dreamer MCP

comfyui_convert_workflow

Convert a ComfyUI UI-format workflow into an API-format file for direct use, resolving Set/Get nodes, reroutes, and bypassed nodes without running the workflow first.

Instructions

Convert a UI-format workflow saved in ComfyUI (e.g. "comfyui:MY_FLOW.json") to API format and save it as workflows/api/.json, without having to run it first. Resolves Set/Get nodes, reroutes and bypassed nodes. Not for workflows with subgraphs.

Args: include_bypassed: Treat bypassed nodes as active (e.g. optional LoadImage slots that are bypassed in the editor but should exist in the API version).

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": {
      "workflow": "<workflow>",
      "name": "<name>"
    },
    "name": "comfyui_convert_workflow"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`workflow`	Yes
`overwrite`	No
`include_bypassed`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool resolves Set/Get nodes, reroutes, and bypassed nodes, and notes the subgraph limitation. It also explains the include_bypassed parameter's effect. However, it does not mention the behavior of the overwrite parameter or error conditions, but the core behavioral details are adequately covered.

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?

The description is concise and well-structured. It starts with the primary purpose, adds a limitation sentence, and then includes an Args section for parameter clarification. Every sentence contributes value without unnecessary fluff, making it easy for an agent to quickly understand the tool's function and usage.

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?

The description is largely complete for a conversion tool: it states the output location, resolves node types, and explains a parameter. However, it omits any explanation of the overwrite parameter's behavior, which is essential for understanding how the tool handles existing files. Given the output schema exists, return value details are not needed, but the missing parameter semantics reduce completeness.

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?

The schema description coverage is 0%, so the description must compensate. It provides context for workflow and name through the main sentence, and explicitly explains include_bypassed in the Args section. However, the overwrite parameter is completely unexplained, and the description does not fully cover all parameters, leaving a gap for a required boolean parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb (convert), resource (UI-format workflow), and output (API format saved to workflows/api/<name>.json). It distinguishes itself from siblings by focusing on conversion rather than running, saving, or managing workflows, and includes specific details like resolving Set/Get nodes and the subgraph limitation.

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 provides clear context by noting the tool works 'without having to run it first' and explicitly excludes workflows with subgraphs. While it does not name alternative tools directly, the context implies when to use this versus running or saving workflows. It gives a practical usage scenario and a clear exclusion, but lacks explicit contrast with sibling tools.

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