Skip to main content
Glama

Paint by Numbers Generator

Create a paint by numbers from a photo

create_paint_by_numbers
Read-onlyIdempotent

Convert a photo (pet, family, wedding, landscape...) into a paint-by-numbers template. Returns: the numbered outline to paint on, a colour preview of the finished painting, a numbered colour key, and download links (printable SVG and PNG, valid for 30 days). Takes about 5 to 40 seconds.

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

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for repeatable results.
imageYesPublic http(s) URL of the photo (JPEG, PNG or WebP), or a data: URI / base64 data.
detailNosimple = 12 colours, big regions (kids, beginners). medium = 16 colours. detailed = 24 colours, small regions (adults, realistic).medium
paletteNoUse only these paints, as "#rrggbb" or {name, color}. Each colour snaps to the nearest paint.
color_spaceNolab can match human colour perception better.rgb
outline_colorNoLine colour of the outline, e.g. #999999 for light lines.#000000
min_region_sizeNoOverride: remove regions smaller than this many pixels. Bigger = easier to paint.
number_of_colorsNoOverride the number of paint colours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Well beyond the annotations, the description discloses the exact return payload and, importantly, that download links expire after 30 days and that generation takes roughly 5–40 seconds – both material for an agent planning timeouts and follow-up calls. It does not cover failure modes (invalid URL, oversized image) or what happens to artifacts after expiry, which leaves a small gap. readOnlyHint=true is consistent with a stateless generator, though the 30-day downloadable artifacts are worth noting.

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, front-loaded with the action, then an explicit 'Returns:' clause, then a timing note. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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 an eight-parameter generation tool with no output schema, the description is largely complete: it names the return artifacts and the timing envelope, and the schema fully documents inputs. The main residual gap is the absence of any guidance on ordering relative to the sibling tools or on error/timeout handling.

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% and every parameter already carries a rich explanation (detail enum levels, palette snapping behavior, min_region_size, number_of_colors), so the schema does the heavy lifting. The description adds only the reminder that the photo may be a pet/family/wedding/landscape image, which aligns with the 'image' parameter's accepted formats but does not extend parameter meaning.

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?

The description uses a specific verb and resource – 'Convert a photo ... into a paint-by-numbers template' – and narrows the input domain with concrete examples (pet, family, wedding, landscape). It also enumerates the deliverables (numbered outline, colour preview, colour key, printable SVG/PNG), so an agent can distinguish this generation tool from get_photo_upload_link and order_custom_kit without opening the schema.

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 implied rather than stated: the description makes clear this is the step that turns a photo into a template, but it never says when to pick it over the sibling tools (e.g. upload the photo first via get_photo_upload_link, or order a physical kit afterwards via order_custom_kit). No exclusions, prerequisites, or failure guidance are given.

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