Skip to main content
Glama

Upscale an image 2x or 4x

upscale_image

Double an image's width and height with a super-resolution model, which reconstructs edges and texture instead of blurring. Takes images of up to about one megapixel (2.25 on Pro). scale 4 (Pro, up to one megapixel, slower) runs the model twice. Returns a download URL valid for one hour.

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 (Pro).
formatNoOutput format. Default: keep the input format.
image_urlNoPublic http(s) address of the image. Use this or image_base64.
image_base64NoThe image file's bytes, base64-encoded. Use for a local file, e.g. one in the repository.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations it discloses real behavioral traits: the model's reconstruction behavior versus blurring, per-tier input size limits, the Pro requirement and doubled compute cost for scale 4, and that output is an ephemeral download URL valid for one hour (which usefully explains the non-idempotent hint).

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?

Four tight sentences with the core action front-loaded and no filler; every clause carries information. Minor ambiguity in the parenthetical '(2.25 on Pro)', which reads as 2.25 megapixels but requires the reader to infer the unit.

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 helpfully covers the return value and its lifetime, and it handles the scale tiers well. It does not note that one of image_url or image_base64 must be supplied even though no parameter is formally required, which is the one gap an agent could trip on.

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 100%, so the baseline is 3, but the description adds meaning the schema only gestures at: it explains what scale 4 actually does ('runs the model twice'), that it is slower and Pro-gated, and that doubling is the default behavior. It says nothing extra about `format` or the two input-source parameters.

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 opens with a specific verb and resource ('Double an image's width and height') and immediately qualifies the mechanism ('super-resolution model, which reconstructs edges and texture instead of blurring'), which distinguishes it from a naive resize and from siblings like compress_image or convert_image.

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 gives clear operating context: input size ceilings ('up to about one megapixel (2.25 on Pro)') and a decision rule for the expensive path ('scale 4 (Pro, up to one megapixel, slower)'). It never names an alternative sibling or states when not to use this tool, so it stops short of full routing guidance.

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.

Resources