Skip to main content
Glama

Image Upscale

image_upscale

Upscale an image to higher resolution.

Takes an image and upscales it using AI models for enhanced quality. Accepts images as:

  • Public URLs (recommended: chains with text_to_image, and the ONLY way in for a file of your own - chat clients do not pass files through to tools)

  • Data URIs or raw base64 (for callers that already hold the bytes)


Available models:

  • RealESRGAN_x4: input size=128-2048x128-2048

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": "<image>",
      "model": "<model>"
    },
    "name": "image_upscale"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesImage as URL (e.g., from text_to_image result), data URI (data:image/png;base64,...), or base64 string. URLs are recommended when chaining tools to avoid base64 context bloat. Supported formats: JPG, JPEG, PNG, GIF, BMP, WebP. Max 10MB.
modelYesUpscaling model (e.g., 'RealESRGAN_x4')
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden and does disclose base64 context-bloat tradeoffs and a model input-size constraint. However, it is silent on whether the call is asynchronous (the presence of webhook_url/webhook_secret and a check_job_status sibling strongly implies a job model) and says nothing about cost or credit consumption.

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?

Front-loaded with the action, then structured bullets for input formats and models. The sentence 'Takes an image and upscales it using AI models for enhanced quality' largely restates the opening line and could be dropped.

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?

Return values are covered by the output schema and file limits live in the schema, but a tool with webhook parameters and a job-status sibling needs at least a hint about async execution and where the result goes. The model list is also partial, with get_available_models implied but never referenced.

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 baseline is 3, but the description adds real meaning beyond the schema by listing the available model and its 128-2048 per-dimension input constraint. The 'only way in for a file of your own' note also explains why the image parameter accepts URLs versus base64.

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 to higher resolution') and clarifies the input modalities it accepts. It is distinguishable from video_upscale by naming the image resource, though it never explicitly contrasts with image_to_image, which could also change resolution.

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?

Guidance is about input format (URL recommended, required for user-supplied files because chat clients don't pass files through) rather than tool selection. There is no statement of when to choose image_upscale over image_to_image or how it relates to image_upscale_price.

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.