Skip to main content
Glama
djavan-ryuuzaki

Dreamer MCP

by djavan-ryuuzaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

comfyui_upscale

Upscale an image using ComfyUI's default workflow. Provide an image URL, data URI, base64, or existing file name to increase resolution with optional scale and workflow adjustments.

Instructions

Upscale an image with the default upscale workflow (preset "upscale").

image may be a URL, data URI, base64, or the name of a file already in ComfyUI's input folder (e.g. a previous output uploaded with comfyui_upload_file).

Empty arguments keep the workflow's own values. extra sets more workflow params or raw "." overrides; workflow swaps the preset for another workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNo
extraNo
imageYes
scaleNo
previewNo
timeoutNo
workflowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses accepted image input forms, default-preserving behavior for empty arguments, and extra/workflow overrides. However, it does not state what the tool returns, whether it blocks/wait behavior, or any side effects beyond possible file placement.

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?

The description is compact and front-loaded with the main purpose. The image-format guidance is valuable and all sentences earn their place, though it is slightly dense with backticks and parenthetical references.

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?

The tool has 7 parameters, no annotations, and no output schema. The description covers the main entry points but omits the return contract and the behavior of wait/preview/timeout, leaving an agent without enough context to fully interpret the result of the call.

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%, so the description must compensate. It adds real meaning for image, extra, and workflow, and notes that empty arguments keep the workflow's own values. It does not explain scale, wait, preview, or timeout, though these are mostly inferable from their names and defaults.

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 first sentence names a specific operation and workflow preset (upscale, preset 'upscale'), making it immediately clear what the tool does and distinguishing it from siblings like comfyui_generate_* or comfyui_run.

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 gives a clear use case: upscaling an image with the default upscale workflow. It does not explicitly rule out siblings or list alternatives, but the scope is specific enough for an agent to select it over the other ComfyUI tools.

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