Skip to main content
Glama

Image Upscale

image_upscale

Upscale an image to higher resolution using AI models, improving quality for low-resolution or small images supplied as URLs, data URIs, or base64.

Instructions

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)

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 observedv0.6.3

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does explain non-obvious behavior: AI-model-based enhancement, the URL-vs-base64 tradeoff around context bloat, and that chat clients can't forward files. But it omits cost implications, expected processing time, and whether the call is synchronous or a queued job requiring check_job_status - all material for an unannotated paid generation tool.

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?

Front-loaded one-line purpose, then a short mechanism sentence, then a two-item bullet list of accepted input forms. Every sentence adds information and the alternatives are formatted for scanning; nothing is padding.

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?

An output schema exists so return values need no explanation, and all four parameters are documented in the schema. What's missing is the operational picture: whether this is async, cost, size/duration expectations, and the relationship to the price and job-status siblings - substantial for a paid AI generation endpoint.

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; the description earns above that by explaining why one format is preferable (URL avoids base64 context bloat) and that the caller may not be able to pass files at all. The model and webhook parameters are not discussed here, but their schema descriptions are detailed enough to compensate.

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" with the mechanism (AI models). It implicitly separates the tool from video_upscale by scoping to images, but never names a sibling such as image_upscale_price, so differentiation relies on the reader inferring it from the name.

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?

Gives real guidance on how to supply input (URL recommended, chains with text_to_image) and notes that chat clients do not pass files through, which is a useful precondition. However, it never states when to pick this tool over image_to_image or the price-check sibling, nor when to avoid it (e.g., file already downscaled, size limits hit).

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