Skip to main content
Glama

upload_image

Loads an image into ComfyUI’s input folder from a local path, URL, or Base64 data, returning the filename to use when rendering.

Instructions

Puts a picture into ComfyUI's input folder. Give ONE of: path (a file on this PC), url (http/https), base64_data (the image bytes; give a name like "cat.png"). Returns the name to use in render(image=...).

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": "upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
nameNo
pathNo
base64_dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, and the description adds real context: the file is persisted into ComfyUI's input folder and the call returns a name for later use. It doesn't address overwrite behavior when a name already exists, size limits, or what error surfaces for an unreachable URL, which matters for a write-side tool.

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?

Two tight sentences with no filler; the core action is front-loaded and the parameter rule and return contract follow in the order an agent needs them.

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?

With no output schema, the description correctly covers the return value, and all four parameters are addressed at least minimally. Given a four-param upload tool, the remaining gaps (overwrite semantics, size limits, error behavior) are moderate rather than disqualifying.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the semantics and it largely does: path is 'a file on this PC', url is 'http/https', base64_data is 'the image bytes', and 'Give ONE of' establishes mutual exclusivity that the schema's four optional properties do not express. The name parameter is only illustrated via base64_data ('give a name like "cat.png"'), leaving its role for path/url uploads slightly ambiguous.

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 states a specific verb and resource ('Puts a picture into ComfyUI's input folder'), names the destination, and ties the result to the sibling tool render(image=...), so an agent can place it in the workflow without opening another schema.

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?

It clearly frames usage: supply exactly one source (path, url, or base64_data) and use the returned name in render(image=...). That gives a clear context and chaining rule, though it offers no explicit exclusions or failure conditions.

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