Skip to main content
Glama

Image Upscale Price

image_upscale_price

Calculate price for image upscaling.

Pass the image, or its width and height.


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": {
      "model": "<model>"
    },
    "name": "image_upscale_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageNoImage to quote (URL, data URI or base64); its size is read from it
modelYesUpscaling model name
widthNoImage width in pixels (required if image not provided)
heightNoImage height in pixels (required if image not provided)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never states that this is a non-mutating quote operation, whether quoting consumes balance or credits, or whether the price depends on model/size tiers, so the agent must assume the side-effect profile. Naming the single available model with its input-size range is the only real behavioral detail provided.

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?

The core action and the input alternatives are front-loaded in the first two lines, and the model block is short and scannable. The `---` divider and orphaned closing quote are minor structural noise but nothing is wasted.

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 the one model's constraint is documented. Still missing is any statement of the quoting/mutation relationship with image_upscale, and the stated 128-2048 input bound sits uneasily beside schema maxima of 10240 for width/height, which could confuse an agent reasoning about valid sizes.

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 would be a 3, but the description adds meaning beyond the schema by enumerating the model value (`RealESRGAN_x4`) even though the schema declares no enum, and by giving its input-size constraint. That saves the agent from guessing valid model strings.

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?

"Calculate price for image upscaling" gives a specific verb (calculate price) and resource (image upscaling), which distinguishes it from the sibling mutation tool image_upscale. It does not explicitly contrast itself with image_upscale or the other *_price siblings, so the differentiation is implied by the name and verb rather than stated.

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?

"Pass the image, or its width and height" tells the agent how to supply input, which is useful usage context. However, it never states when to call this versus performing image_upscale, or whether a quote should precede an actual upscale job, leaving the workflow relationship to inference.

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.