Skip to main content
Glama

Colors a black-and-white manga page you name with a Workers

media_manga_colorizer
Read-only

Colors a black-and-white manga page you name (public image URL, PNG or JPEG up to 4 MB) with a Workers AI image-to-image model. Output is a generated image, not the original artwork; colors are model guesses. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "media_manga_colorizer"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoShort style prompt, 3 to 200 characters (optional)
image_urlYesPublic https URL of a PNG or JPEG image

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing that output is a generated image rather than the original artwork, that colors are model guesses, and that billing is $0.002 per successful call via x402 with failures not charged. The only minor gap is no note on typical latency, image size, or output dimensions, but that is thin territory given the annotations and output schema.

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 tight sentences, front-loaded with the action and input format, with pricing last. The 'Solana and 10 more networks' enumeration is slightly padded but still relevant to a paying agent deciding whether it can complete payment.

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 an output schema present, the description needn't detail return values, and it still flags the critical output caveat that the result is a model-generated recolor. Cost, payment rail, failure billing, and input constraints are all covered for a 2-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema lacks: a 4 MB size ceiling and the public-https requirement for image_url. The optional style parameter is not elaborated in prose, but its schema description (3-200 characters) is adequate.

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?

States a specific verb and resource ('Colors a black-and-white manga page') plus the mechanism ('Workers AI image-to-image model'). The scope is unambiguous even without sibling differentiation, since the listed siblings are unrelated domains.

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?

The description supplies input preconditions (public https PNG/JPEG under 4 MB) and cost gating, which implicitly frames when the tool applies. It never states when not to use it or names any alternative path, so guidance remains implied rather than explicit.

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