Skip to main content
Glama
djavan-ryuuzaki

Dreamer MCP

by djavan-ryuuzaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

comfyui_run

Queue a ComfyUI workflow using friendly params, raw node overrides, or inline JSON. Optionally randomize seeds, wait for job completion, and return image outputs with previews.

Instructions

Queue a workflow on ComfyUI.

Args: workflow: Workflow name from comfyui_workflows. params: Friendly params defined in workflows.yaml, e.g. {"prompt": "a cat", "steps": 20}. inputs: Raw node overrides, keyed ".", e.g. {"6.text": "a cat", "KSampler.cfg": 6.5}. workflow_json: An inline API-format workflow, used instead of workflow. randomize_seed: Give seed/noise_seed inputs that were not set explicitly a new random value (otherwise ComfyUI may return a cached result and skip execution). wait: Block until the job finishes (or timeout seconds) and return its outputs. timeout: Seconds to wait when wait=true (default DEFAULT_WAIT_TIMEOUT). preview: With wait=true, also return downscaled previews of the resulting images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNo
inputsNo
paramsNo
previewNo
timeoutNo
workflowNo
workflow_jsonNo
randomize_seedNo

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?

With no annotations, the description carries the full behavioral burden. It discloses important runtime behavior: randomize_seed prevents cached results, wait blocks until completion and returns outputs, timeout bounds the wait, and preview returns downscaled images. It does not mention side effects like queue consumption or failure modes, but the provided behavioral details are substantial.

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 front-loaded with a one-sentence summary followed by a tight Args list. Each parameter line adds necessary detail, including examples and edge-case behavior, with no filler or repetition.

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?

The description is thorough for a complex 8-parameter tool with no output schema, explaining all parameters and key behaviors. However, it does not state that at least one of workflow or workflow_json is required, nor what is returned when wait=false. These are minor but meaningful gaps for an agent invoking the tool.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description documents all 8 parameters with meaningful semantics and examples. It distinguishes friendly params from raw node inputs, explains workflow_json as an alternative to workflow, and clarifies the role of randomize_seed, wait, timeout, and preview. This fully compensates for the bare schema.

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 opening line 'Queue a workflow on ComfyUI' uses a specific verb and resource, making the tool's core function immediately clear. It is distinct from sibling tools like comfyui_status or comfyui_workflow_info, and the workflow-focused action differentiates it from generation helpers.

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 explains what the tool does but provides no explicit guidance on when to choose it over alternatives such as comfyui_generate_image or comfyui_workflow_info. There are no exclusion criteria or 'use this instead of X' statements, leaving the agent to infer the appropriate context.

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

Deploy Server

Other Tools