Skip to main content
Glama

old_photo_restore

Restore an old photograph: scratches, fading, stains, creases. Returns { processedImage }. Cost: 3 credits.

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>"
    },
    "name": "old_photo_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesImage as a base64 data URI (data:image/png;base64,…) or an HTTPS image URL
optionsNoRestoration steps to apply (the app turns all of them on)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does add two genuinely useful behaviors absent from structured data: the return shape { processedImage } and a cost of 3 credits. It says nothing about permissions, failure modes, or processing latency, and never states that it mutates/consumes credits beyond the price tag.

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?

Two compact, front-loaded sentences: capability first, then return value and price. The only mild redundancy is the defect list echoing the schema's option names, but it efficiently conveys scope.

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?

For a simple one-required-param tool with rich schema descriptions, the definition covers capability, return shape, and cost, which is close to sufficient. The absence of annotations means it should say more about side effects and whether credits are charged on failure.

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 100%, so both the base64/URL image format and each options flag are already documented. The description's defect list mirrors the option names without adding format, precedence, or default behavior beyond what the schema states (the schema itself notes all options default on). Baseline 3 applies.

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+resource ("Restore an old photograph") and enumerates the defect classes it handles (scratches, fading, stains, creases), so the agent knows exactly what the operation does. It stops short of distinguishing itself from plausible siblings like photo_repair or enhance_image.

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?

The phrase "old photograph" implicitly scopes usage, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative for related tasks such as repair or enhancement. The agent must infer routing from sibling names alone.

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