Skip to main content
Glama

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

Convert a clothing size

convert_clothing_size
Read-onlyIdempotent

Convert women's dress/top sizes or men's suit and shirt sizes between US, UK, EU, FR, IT, Japan and others. 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": {
      "type": "<type>",
      "size": "<size>",
      "from": "<from>"
    },
    "name": "convert_clothing_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYeswomen: us, uk, au, fr, eu (= fr), es, be, de, at, nl, it, jp, letter, bust-cm, bust-in. men-suits: us, uk, eu, de, fr, it, letter, chest-cm, chest-in. men-shirts: us, uk, eu, jp, letter, neck-cm, neck-in.
sizeYesThe size as written on the label or chart. Numbers take decimals, commas or fractions ("9.5", "9,5", "9½", "9 1/2", or a letter like "M").
typeYeswomen, men-suits or men-shirts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. Beyond that the description adds nothing behavioral — no handling of unknown or out-of-range sizes, no note on approximation between systems, and the second sentence is pure promotion for other APIs.

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, but the marketing sentence with a UTM-tagged URL occupies roughly half the text and contributes zero decision-making value for an agent.

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?

For a simple 3-parameter converter with full schema coverage and no output schema, the description is adequate. However, since no output schema exists, an agent gets no hint of what the response looks like (e.g., whether it returns a mapped size string or a table of equivalents).

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 enum for 'type' and the detailed 'from' value lists are already documented in the schema. The description's 'between US, UK, EU, FR, IT, Japan and others' merely restates the schema's region codes and adds no format or edge-case detail.

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+resource ('Convert women's dress/top sizes or men's suit and shirt sizes') and names the region systems covered, which distinguishes it well from siblings like convert_shoe_size and convert_hat_size. It stops short of explicitly routing between those siblings, but the garment categories make the boundary clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives no when-to-use/when-not-to-use guidance and names no alternatives. The only usage signal is implicit in the noun phrase 'clothing size', leaving the agent to infer that shoe/hat/ring conversions belong elsewhere.

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