Skip to main content
Glama
veniceai

Venice MCP Server

Official
by veniceai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Venice Image Upscale

venice_image_upscale

Upscale an image from a URL by 2-4x and return a base64 PNG, converting the URL to base64 for the Venice API and respecting 4096x4096 output limits.

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.

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_urlYes
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. 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
  2. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only carry the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds genuinely useful behavior beyond that: it normalizes the base64 requirement by fetching the URL itself, declares the base64 PNG return format, and reveals two auth paths (x402 wallet or API key). It stops short of stating failure behavior or rate limits.

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?

Three tight sentences, front-loaded with the core action, then the URL-fetch mechanics, then return format and auth. Every sentence carries information; only the scale range in parentheses mildly duplicates the schema.

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 fills that gap by declaring a base64 PNG return, and it covers auth requirements. For a single-required-parameter image tool this is nearly complete; only error modes and payload-size limits are absent.

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 coverage is 67%: scale and creativity are already fully documented in the schema, while image_url carries no description there. The description adds the useful detail that the tool fetches that URL and uploads it, but no syntax, size, or format guidance for the URL itself. Baseline 3 is appropriate.

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?

The description states a specific verb and resource (upscale an image) plus the scale range, which is enough to distinguish it from venice_image_edit and venice_image_generate. It does not, however, explicitly name or contrast itself against those siblings, leaving the agent to infer the boundary.

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 implied rather than stated: the agent can infer this is for enlarging an existing image, but the description never says when to choose it over venice_image_edit, venice_image_multi_edit, or venice_image_generate, nor what preconditions apply. No exclusions or alternatives are offered.

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