Skip to main content
Glama

Cross Stitch Pattern Maker

Order a custom cross stitch kit

order_custom_kit
Read-only

Make a checkout link for a real custom cross stitch kit of the person's photo from Cross Stitched: printed pattern chart, pre-sorted DMC threads, Aida fabric, needles and instructions, delivered. The person pays on the Cross Stitched checkout; nothing is charged by this tool. Give pattern_id (from create_cross_stitch_pattern) or photo_id.

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
framedNoFramed kit. Default false.
kit_sizeNoKit size, e.g. "12x16". Default: the size used for the pattern, else 12x16.
materialNoThread type. Default Cotton.
photo_idNoPhoto code (ph_...) from the upload page, if no pattern was made.
quantityNoNumber of kits. Default 1.
pattern_idNoPattern id (pt_...) from create_cross_stitch_pattern.
fabric_countNoDefault: the count used for the pattern, else 14.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds real value beyond that by explaining the payment boundary — the tool charges nothing and the person pays externally on the Cross Stitched checkout. It stops short of disclosing link lifetime, single-use behavior, or whether repeated calls mint multiple links, which matters for an open-world external handoff.

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?

Three sentences, front-loaded with the action and the no-charge caveat before the input instruction. The kit-contents clause is long but earns its place by substantiating 'real' kit, though it could be trimmed without loss.

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?

With 7 all-optional parameters, no required fields, and no output schema, the key risk is ambiguity about which identifier to supply, and the description resolves that. What it omits is any indication of what the returned artifact looks like (a URL string) or how long it stays valid, which would round out an external-handoff tool.

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% and each parameter already carries a description with defaults, so the baseline applies. The description does add one piece of genuine meaning the schema cannot express: that pattern_id and photo_id are alternative entry paths with different origins, which is a one-of relationship absent from the flat object schema.

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 opens with a specific verb and resource ('Make a checkout link for a real custom cross stitch kit'), then enumerates exactly what the kit contains and how delivery works. It also distinguishes itself from siblings by naming create_cross_stitch_pattern as the source of pattern_id, so an agent knows this is not the pattern-creation or pricing tool.

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?

It gives clear triggering context ('The person pays on the Cross Stitched checkout; nothing is charged by this tool') and tells the agent the required input choice ('Give pattern_id ... or photo_id'). What's missing is explicit routing to get_kit_prices or get_photo_upload_link for the pre-checkout steps, so the alternative-selection guidance is implied rather than stated.

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.