Skip to main content
Glama

Upscale ×2

upscale_image

Doubles the size of a picture with Topaz (from the Дизайн plan, charged in credits). Give job_id of one of your genframe pictures or image_url.

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
job_idNo
image_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a mutating, open-world, non-idempotent, non-destructive call, so credit is limited to what is added. The description does add real cost context: it runs on Topaz under the Дизайн plan and bills in credits. It says nothing about whether a job is created asynchronously, how long processing takes, or what happens to the original asset.

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 compact sentence plus a short input directive; the core action and the credit cost are front-loaded and nothing is wasted.

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 two-parameter, no-output-schema tool this covers the essentials: what it does, the engine, the billing plan, and where the source image comes from. What is missing — async job semantics and the relationship between the two optional parameters — is a modest but real gap.

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 coverage is 0%, so the description must compensate, and it partially does: job_id is constrained to 'one of your genframe pictures', which rules out arbitrary job identifiers. However it never says the two parameters are alternatives to exactly one of which must be supplied, gives no format for image_url, and does not state precedence if both are passed — both are also marked optional in the schema.

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 ('Doubles the size of a picture') plus the engine used (Topaz), so the operation is unambiguous. It does not differentiate itself from siblings such as generate_image or vectorize, but the name-plus-description pair leaves little doubt about the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over the other image-producing tools, no preconditions, and no exclusions. The only directional hint — that the source must be one of your genframe pictures or a URL — describes input, not usage context.

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