Foca Upscaler

Create an image upscaling task

upscale_image

Idempotent

Create a paid asynchronous task from an HTTPS image URL using the physics engine. Requires an active paid subscription or a previously successful credit-pack purchase, sufficient credits, and tier access under the account's plan. The 2K/4K/8K/16K tiers cost 15/30/60/120 credits. Retry the same request with the same idempotency_key, image URL, and resolution_tier.

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_url": "<image_url>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "upscale_image"
  }
}

Input Schema

Name	Required	Description
`image_url`	Yes	Publicly retrievable HTTPS image URL.
`idempotency_key`	Yes	A 1–128 character key. Preserve it when retrying the same image URL and tier. Idempotency records are retained for at least 30 days; after retention expires, reusing an old key may create a new task and charge credits again.
`resolution_tier`	No	Output tier: 2, 4, 8, or 16. Defaults to 2.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent, open-world, non-destructive. The description adds genuinely new behavioral facts the annotations lack: the operation is asynchronous, it is paid, and it consumes credits at 15/30/60/120 for the 2K/4K/8K/16K tiers. It stops short of describing how completion is observed, but the cost and async nature are the important disclosures.

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?

Three sentences, front-loaded with the core action before prerequisites, costs, and retry semantics. The prerequisites sentence is dense but every clause carries a distinct requirement; no filler or restatement of the tool name.

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?

An output schema exists, so return values need not be explained. The description covers preconditions, cost, async nature, and safe retry, which is nearly everything needed. The one gap is not pointing to get_upscale_task as the way to observe the asynchronous result.

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 mapping each resolution_tier value to its credit price (15/30/60/120), which the enum alone does not convey. The idempotency and URL semantics largely restate what the schema properties already document.

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?

States a specific verb and resource ('Create a paid asynchronous task') plus the input medium ('from an HTTPS image URL'). Together with the sibling names get_upscale_info and get_upscale_task, an agent can immediately tell this is the task-creation entry point rather than a status/info lookup.

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?

Clear preconditions are given: active paid subscription or prior credit-pack purchase, sufficient credits, and tier access under the account's plan. The retry instruction ('Retry the same request with the same idempotency_key...') tells the agent how to use it safely. It does not, however, explicitly route to get_upscale_task for polling completion, so the alternative-selection guidance is implicit.

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

All Foca Upscaler tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?