Skip to main content
Glama

Paint by Numbers Generator

Order a custom paint by numbers kit

order_custom_kit
Read-only

Get the link to order a real custom paint-by-numbers kit of the person's own photo from paint-by-number.com (pre-printed canvas, numbered pre-mixed paints and brushes, delivered). Use when the person wants to paint the result for real, wants a gift, or asks where to buy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "order_custom_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantial context beyond them: the return value is a link (not a placed order), the ordering happens on an external commercial site, and the deliverable is a physical shipped product. It does not mention cost, shipping regions, or account requirements for the external site, which would be the remaining useful disclosures.

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 sentences, front-loaded with what the tool returns, followed by when to use it. No redundant restatement of the title and no filler.

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?

For a zero-parameter tool with no output schema, the description covers everything an agent needs: it returns a URL rather than performing a purchase, the destination is external, and the product is a physical item. 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.

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly implies nothing user-specific needs to be supplied at call time.

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: 'Get the link to order a real custom paint-by-numbers kit' of the user's own photo, with the supplier named (paint-by-number.com). The physical-product framing ('pre-printed canvas, numbered pre-mixed paints and brushes, delivered') separates it in practice from create_paint_by_numbers, though no sibling is named explicitly.

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?

Gives three concrete triggering conditions: the person wants to paint the result for real, wants a gift, or asks where to buy. Clear positive context, but no exclusions and no explicit pointer to the sibling tools for the case where the user only wants the generated image.

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