Skip to main content
Glama

photo_repair

Fix blur, noise, low resolution or general damage in a photo. Returns { processedImage }. Cost: 2 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": "photo_repair"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRepair type (default restore)
imageYesImage as a base64 data URI (data:image/png;base64,…) or an HTTPS image URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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; it does add two genuinely useful facts beyond structured data — the return shape ({ processedImage }) and a fixed cost of 2 credits. It is silent on whether the source image is preserved, whether the call is synchronous or how long it takes, output format/resolution, and any input limits, all of which matter for an image-mutating tool.

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?

Three short sentences with zero filler: capability first, return value second, cost last. Every sentence earns its place and the most decision-relevant information is front-loaded.

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?

For a simple two-parameter tool, the description plus a 100%-covered schema and a stated return shape cover most of what an agent needs to invoke it correctly. The remaining gap is behavioral rather than structural — no annotations means storage, latency, and output-format expectations go unstated.

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 parameters are already fully documented, and the enum values (restore, unblur, denoise, upscale) map onto the defect list in the description only loosely. No extra detail on accepted input forms or defaulting behavior beyond what the schema states, so 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 and resource ('Fix blur, noise, low resolution or general damage in a photo') and enumerates the defect classes it handles, so the agent knows exactly what operation it performs. It does not, however, distinguish itself from siblings such as old_photo_restore, enhance_image, or portrait_retouch, leaving overlap unresolved.

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?

Usage is only implied: the list of defects signals 'use this when the photo is blurry/noisy/low-res/damaged', which is a reasonable trigger. There is no explicit when-not guidance and no mention of the closely related siblings (old_photo_restore, enhance_image) that an agent would need in order to choose correctly.

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