Skip to main content
Glama

Cross Stitch Pattern Maker

Get custom kit prices

get_kit_prices
Read-only

Get live prices for a custom photo cross stitch kit from Cross Stitched (cross-stitched.com): every size, Cotton or Silk thread, 11 or 14 count, plus the current offer. Filter with the optional arguments.

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

Input Schema

NameRequiredDescriptionDefault
framedNoOptional. Framed kits only (true) or unframed only (false).
kit_sizeNoOptional. e.g. "12x16".
materialNoOptional. Thread type.
fabric_countNoOptional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is lighter, and it still adds real value: 'live prices' signals dynamically fetched external data and 'current offer' warns that a promotional figure may appear alongside base pricing. It stops short of stating currency, whether shipping is included, or how the price list is structured in the response.

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?

A single front-loaded sentence with the source site named up front and the option list following. The enumeration is dense but each element conveys a real pricing dimension; the closing sentence about filtering is the weakest, since it restates that the arguments are optional.

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 zero-required-parameter read-only lookup with no output schema, the description does its main job by telling the agent what the returned price set spans. Gaps are minor but real: no currency, no indication of whether discounts/offer data is a separate field, and no mention of the framed filter.

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%, so the schema already documents all four optional filters, putting this at the baseline. The description mirrors three of them (size, thread material, fabric count) but never mentions the 'framed' filter, so it adds no meaning beyond what the schema supplies.

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?

The description names a specific verb and resource ('Get live prices for a custom photo cross stitch kit') and enumerates the priced dimensions (size, Cotton/Silk, 11/14 count, current offer). It implicitly separates itself from siblings like order_custom_kit or create_cross_stitch_pattern, but never names or contrasts an alternative explicitly.

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: 'Filter with the optional arguments' tells the agent the parameters narrow results but gives no when-to-use framing, no prerequisites, and no statement of when another sibling (e.g. ordering) would be the right call instead.

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.