Skip to main content
Glama
Sign In
Medhā MCP

Medhā MCP

by vivmuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Venice Image Upscale

venice_image_upscale

Upscale any image URL 1-4× with optional enhancement and replication control. Get a high-resolution PNG output for improved quality.

Instructions

Upscale an image (1-4× scale). Endpoint requires base64 image; this tool fetches the URL and uploads it. Returns base64 PNG. Operator preferences — default: flux-2-pro; also try: nano-banana-pro. 1-4× enhancement + replication control. 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 1-4. 1 = enhance only.
enhanceNo
image_urlYes
replicationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0-medha

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses key behaviors: it fetches URLs itself instead of accepting base64 directly, handles alternative auth (x402 wallet, no Venice account needed), returns base64 PNG, and mentions operator preference details (default flux-2-pro, nano-banana-pro). This is rich operational transparency for a tool with zero annotations.

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 reasonably compact at around 50 words and front-loaded with the core action. The operator preference and auth details are useful additions. Slightly dense with multiple clauses, but each sentence contributes meaningful information without waste.

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?

For a 4-param tool with no output schema and only 25% schema coverage, the description is fairly complete: it covers the input handling, output format, scale/effect scope, operator defaults, and auth requirements. Minor gaps: the exact interaction between enhance and replication parameters and what 'replication control' means operationally are not fully specified, but given zero annotations, this is strong coverage.

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 only 25% (only image_url and scale have schema descriptions), so the description partially compensates by clarifying scale meaning and image handling. However, it doesn't explain 'enhance' and 'replication' parameter semantics beyond their schema names, leaving their meaning and interaction somewhat ambiguous despite the description mentioning 'enhancement + replication control' in general terms.

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+resource ('Upscale an image') with scale range (1-4×), clearly distinguishing from siblings like venice_image_generate/edit/remove_bg. It also covers the operational mechanism (fetches URL, uploads base64) and output format (base64 PNG).

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 implies context primarily through specifying 'enhancement + replication control' and the scale semantics. It doesn't explicitly say when NOT to use it or name alternatives, but the mechanical detail about URL fetching vs base64 endpoint and auth options (x402 wallet vs API key) provides useful decision context. Lacks explicit exclusions or sibling comparison.

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