Skip to main content
Glama

Upscale image

upscale_image

Upscale an image 2× (source up to 16 MP, 2 credits) or 4× (source up to 4 MP, 4 credits) with Real-ESRGAN. Needs paid credits.

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

Input Schema

NameRequiredDescriptionDefault
scaleNo2 (default) or 4.
formatNoOutput format. png keeps transparency everywhere; webp is smaller; jpg has no transparency.
image_urlNoPublic http(s) URL of a JPG, PNG or WebP image (up to 25 MB).
image_base64NoThe image as base64 (or a data: URL), if there is no public URL. Prefer image_url for large files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations only declare that this is a non-read-only, open-world, non-idempotent, non-destructive operation; the description adds genuinely new behavioral facts: a per-call credit cost that scales with mode, the hard requirement of paid credits, and source resolution ceilings. It stops short of describing the response payload or failure behavior when credits are insufficient.

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?

One dense sentence that front-loads the action, then the two priced modes, then the model and the credit prerequisite. No filler, no repetition of the title, and every clause carries a distinct constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of explaining what comes back from the upscale (URL, binary, expiry), and it says nothing about that. Cost, prerequisites, and input limits are well covered, so an agent can call it correctly but cannot predict the result shape.

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 description coverage is already 100%, so the baseline is 3, but the description adds meaning the schema lacks: the MP limits attached to each scale value, which tells the agent when a given source image will be rejected. It does not elaborate on format or base64 tradeoffs beyond what the schema already says.

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?

States a specific verb and resource ('Upscale an image') and immediately quantifies the two modes (2× vs 4×) plus the underlying model (Real-ESRGAN). The operation is unambiguously distinct from the siblings erase_objects, remove_background, and get_credits without needing to name them.

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?

The MP ceilings per scale factor (16 MP at 2×, 4 MP at 4×) implicitly guide the choice between the two modes, and 'Needs paid credits' flags a prerequisite. However, there is no explicit when-to-use or when-not guidance relative to sibling tools such as remove_background, and no statement about what to do when the source exceeds the MP limit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.