Skip to main content
Glama

Restore an old photo

restore_photo

Repair an old or damaged photo: remove scratches, dust, creases and fading, recover sharp faces, keep everyone exactly as they are. Optionally colorize a black-and-white photo. Costs credits. Returns the restored image (or pending → get_image). Tip: animate the result with animate_photo afterwards.

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

Input Schema

NameRequiredDescriptionDefault
colorizeNoAlso colorize a black-and-white or sepia photo. Default false.
image_urlYesPublic https URL of the old photo (a scan or phone photo of a print is fine).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, not destructive, open-world); the description adds substantive behavior: it costs credits, it may return a pending state requiring get_image, and it preserves subjects' identity ('keep everyone exactly as they are'). Credit amounts and failure modes are not covered, keeping it below 5.

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?

The core action is front-loaded, followed by the optional colorize flag, cost note, return/pending semantics, and a chained-next-step tip. Dense with zero filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps in to explain what comes back (restored image, or pending routed to get_image) and what it costs. For a two-parameter tool with annotations covering safety, nothing material is missing for correct invocation.

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 both parameters are already documented, including colorize's default of false. The description's mention of optional colorization for black-and-white photos restates rather than extends the schema, which is the baseline-3 case.

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?

Names a specific verb and resource (repair an old or damaged photo) and enumerates the exact defects handled: scratches, dust, creases, fading, soft faces. This is clearly a restoration tool, distinct from siblings like create_image or edit_video.

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 description establishes context (old/damaged photos, scans or print photos per the schema), notes the optional colorize path, and explicitly routes the agent onward: 'animate the result with animate_photo afterwards' and 'pending → get_image'. It doesn't state explicit exclusions versus create_image, but the intended use case is unambiguous.

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