Skip to main content
Glama
Sign In

ImgKits MCP

by io.github.yichong1
OverviewDiscussionsAdmin

Upscale image

upscale_image

Upscale an image from a public URL. POST {img, upscale} to ai.imgkits.com/api/restoration. scale is 2 (default) or 4 and is sent as upscale. Optional face_enhance is sent on the same body. There is no separate enhance_photo or enhance_face tool. Synchronous. Cost: 2 credits per call; mcp-credit-gateway charges before forwarding.

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": {
      "source_url": "<source_url>"
    },
    "name": "upscale_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoScale factor sent to the restoration upstream as `upscale`. 2 (default) and 4 are the supported factors. Face enhancement is the optional `face_enhance` flag on this same tool; there is no separate enhance tool.
bucketNoOptional upstream storage bucket. Sent only when set here or via RESTORATION_BUCKET.
source_urlYesPublic http(s) URL of the image to upscale (JPG/PNG/WebP).
face_enhanceNoWhen set, forwarded as `face_enhance` on the restoration body. Omit it to send only `img` and `upscale`.
idempotency_keyNoOptional caller correlation key, echoed in the result. Billing is handled by mcp-credit-gateway.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, openWorldHint=true, destructiveHint=false), yet the description adds material context beyond them: the call is synchronous, costs 2 credits, and mcp-credit-gateway charges before forwarding. What is missing is failure/refund behavior when the upstream call fails after the charge is taken.

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 and dense: endpoint, parameter mapping, the negative routing note, synchronicity, and cost arrive in five short sentences with no filler. Some of that runtime detail (the exact 2/4 scale values) duplicates schema content and could be trimmed.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it only says the call is synchronous without describing the returned payload (image URL, echo of idempotency_key). For a 5-parameter billing-charged tool that is an adequate but incomplete definition.

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 description coverage is 100%, so the baseline is 3, and the description largely restates what the schema already declares — that scale is 2 or 4 and is sent as `upscale`, and that face_enhance rides the same body. It says nothing at all about `bucket` or `idempotency_key`, so it adds little meaning beyond the structured fields.

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?

Opens with a specific verb+resource ("Upscale an image from a public URL") and further pins down the mechanism (POST {img, upscale} to ai.imgkits.com/api/restoration). It also explicitly negates a plausible wrong assumption by stating there is no separate enhance_photo or enhance_face tool, so an agent can rule out siblings without opening schemas.

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?

The input precondition "public URL" is stated, and the description explicitly closes off the alternative enhance tools an agent might otherwise search for. It stops short of differentiating from other image siblings like colorize_photo or translate_image, so it is clear context rather than full when/when-not routing.

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

All ImgKits MCP toolsInspect
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