Skip to main content
Glama

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

Convert a shoe size

convert_shoe_size
Read-onlyIdempotent

What is a US men's 10 in EU, UK, Japan or Mondopoint? Convert shoe sizes between systems for men, women and kids, through foot length. 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": {
      "size": "<size>",
      "from": "<from>",
      "group": "<group>"
    },
    "name": "convert_shoe_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe size system of "size".
sizeYesThe size as written on the label or chart. Numbers take decimals, commas or fractions ("9.5", "9,5", "9½", "9 1/2", "42 2/3" for EU thirds, "10.5C" or "3Y" for US kids).
groupYesmen, women or kids: picks the US and UK scales.
womenScaleNoUS women's scale: common (men's + 1.5, default) or fia (men's + 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral detail — that conversion is done 'through foot length', which explains why results may be rounded rather than exact table lookups. It says nothing about rounding precision, output shape, or how ambiguous sizes are resolved.

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 question-form opening is well front-loaded and the second sentence states the purpose efficiently. However, the third sentence is a promotional link to 'More APIs from FitzTopPicks' with UTM parameters, which does nothing to help an agent select or invoke this tool and dilutes an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining what comes back — and it does not, leaving ambiguous whether the tool returns one converted value or conversions across all systems, nor whether rounding/precision is reported. For a 4-parameter, read-only conversion tool with rich enum and format documentation in the schema, this is adequate but clearly incomplete.

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 the schema already documents the from-system enum, the label-as-written size format (decimals, commas, fractions, kids suffixes) and the womenScale option in detail. The description only gestures at the systems ('EU, UK, Japan or Mondopoint') and the men/women/kids grouping, adding essentially no syntax or semantics beyond the schema, so the baseline of 3 applies.

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 ('Convert shoe sizes between systems') and scopes it to men, women and kids, so it is clearly not clothing, hat or ring conversion. It never explicitly names or routes against the neighbouring converters (convert_clothing_size, convert_hat_size, convert_ring_size) or the chart/reference tools, so it stops short of full sibling differentiation.

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 opening question ('What is a US men's 10 in EU, UK, Japan or Mondopoint?') implies the typical use case, but there is no explicit when-to-use/when-not guidance and no mention of when to prefer size_chart or size_systems instead. An agent can infer usage from the example but must guess at the boundaries.

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