Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Image Upscale

venice_image_upscale

Upscale images 2-4× from an http(s) or base64 URL input and return a base64 PNG. Increase resolution for print, display, or detail-heavy workflows.

Instructions

Upscale an image (2-4× scale). Endpoint requires base64 image; this tool fetches the URL and uploads it. Returns base64 PNG. Supports x402 wallet auth (no Venice account needed) and API key.

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": {
      "image_url": "<image_url>"
    },
    "name": "venice_image_upscale"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoUpscale factor, 2 to 4. Defaults to 2. Large inputs are scaled down automatically to stay under the 4096x4096 output cap.
image_urlYesImage to upscale: an http(s) URL or an inline base64 data URL. Include a concrete media type in data URLs, e.g. image/jpeg.
creativityNoHow much detail and texture the upscaler invents, 0 to 0.02. Defaults to 0.01. Higher stays further from the source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / image_url / description
      Added value: +"Image to upscale: an http(s) URL or an inline base64 data URL. Include a concrete media type in data URLs, e.g. image/jpeg."
  2. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / creativity
      Added value: +{
      +  "description": "How much detail and texture the upscaler invents, 0 to 0.02. Defaults to 0.01. Higher stays further from the source.",
      +  "maximum": 0.02,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • removedInput schema / properties / enhance
      Removed value: -{
      -  "type": "boolean"
      -}
    • removedInput schema / properties / replication
      Removed value: -{
      -  "maximum": 1,
      -  "minimum": 0,
      -  "type": "number"
      -}
    • changedInput schema / properties / scale / description
      Previous value: -"Upscale factor 1-4. 1 = enhance only."New value: +"Upscale factor, 2 to 4. Defaults to 2. Large inputs are scaled down automatically to stay under the 4096x4096 output cap."
    • changedInput schema / properties / scale / minimum
      Previous value: -1New value: +2
  3. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by explaining that the endpoint requires base64, so the tool fetches the URL and uploads it, and that the result comes back as base64 PNG. It also discloses the two auth paths (x402 wallet with no Venice account, or API key), which is meaningful context for an open-world, non-idempotent call. It does not mention cost implications of x402 payment or request limits.

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?

Three tight sentences, front-loaded with the action, followed by the data-flow caveat and auth options. Nothing is redundant or padded.

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?

Covers what the tool does, how the image is transported, the return format, and the auth paths, which is sufficient for a 3-parameter tool with a fully-annotated schema and no output schema. Only billing/cost behavior for the x402 path is left unstated.

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 100%, so all three parameters are already documented, and the only parameter detail in the description (2-4× scale) simply restates the schema. Baseline 3 applies because the schema carries the semantic load.

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: "Upscale an image (2-4× scale)". This clearly separates it from siblings like venice_image_generate, venice_image_edit, and venice_image_remove_bg, though no sibling is named explicitly.

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?

Usage is only implied: call it when you have an image that needs upscaling. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as venice_image_edit for other transformations.

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