Skip to main content
Glama
Sign In

AirGallery

by com.airgallery
OverviewDiscussionsAdmin

colorize_image

Colorize a black and white photograph. Returns { image }. 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": "colorize_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesImage as a base64 data URI (data:image/png;base64,…) or an HTTPS image URL
styleNoColor style (default natural)

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?

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses a per-call cost of 2 credits and the return shape ({ image }), but says nothing about what happens with non-grayscale inputs, processing time, or failure modes.

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?

Two short sentences, front-loaded with the action, then the return value and cost. Every clause carries information and there is no filler.

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 with a complete schema, the description covers the operation, the return field, and the credit cost, which is enough to invoke it correctly. Minor gaps remain around non-grayscale inputs and output format details, but nothing essential is missing.

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%, with both the image data-URI/URL format and the style enum fully documented in the schema. The description adds no additional parameter meaning beyond what the schema already states, so the baseline of 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 ('Colorize a black and white photograph'), so an agent knows exactly the transformation being performed. It does not distinguish itself from adjacent siblings such as cartoonize, old_photo_restore, or enhance_image, which could plausibly accept the same input.

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 phrase 'black and white photograph' tells the agent the expected input is a grayscale image, but there is no explicit statement of when to pick this over old_photo_restore or enhance_image, and no exclusions or prerequisites.

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

All AirGallery 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