Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

A whole size chart

size_chart
Read-onlyIdempotent

A complete shoe, ring, hat or clothing size chart from one system to every other, for size pickers or listings. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "category": "<category>",
      "from": "<from>"
    },
    "name": "size_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe system whose labels make the rows.
typeNoClothing: women, men-suits or men-shirts.
groupNoShoes: men, women or kids.
categoryYesshoe, ring, hat or clothing.
womenScaleNoShoes: common or fia.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the result is a *complete* cross-system chart (not a single pair), which is real behavioral value, but it says nothing about chart size, whether every system is always included, or how rows/columns are ordered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and efficient. The second sentence is a promotional link ('More APIs from FitzTopPicks...') with UTM parameters that does not help an agent select or invoke the tool, so it fails the 'every sentence earns its place' test.

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 low-complexity, read-only lookup with a fully documented 5-parameter schema and strong annotations, the description supplies enough to call it correctly: the resource, the 'from one system to every other' scope, and the supported categories. The only real gap is the exact shape of the returned chart, which is a minor omission given no output schema exists.

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 relevant parameter carries an enum plus a description, so the schema does the semantic work. The description only restates the category values ('shoe, ring, hat or clothing') already listed in the schema and adds nothing about conditional parameters such as womenScale, group, or type.

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 resource ('a complete shoe, ring, hat or clothing size chart') and the transformation it performs ('from one system to every other'), which is meaningfully different from a single-pair conversion. It does not name or differentiate itself from the sibling convert_shoe_size / convert_ring_size / convert_hat_size / convert_clothing_size tools, so an agent must infer that this one returns the full table rather than one conversion.

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 clause 'for size pickers or listings' gives an implied usage context (bulk/table use rather than a single lookup). However, there is no explicit when-to-use, when-not-to-use, or reference to the per-category converter siblings, so the agent is left to infer that this is the 'whole chart' variant.

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