Skip to main content
Glama

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

Convert a hat size

convert_hat_size
Read-onlyIdempotent

Convert a hat size between US fitted, UK, EU centimeters, inches and S/M/L letters. 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>"
    },
    "name": "convert_hat_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe hat size system: us, uk, eu (cm label), cm or in (measured head), letter.
sizeYesThe size as written on the label or chart. Numbers take decimals, commas or fractions ("9.5", "9,5", "9½", "9 1/2", "7⅛", or a letter like "M").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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. For a pure deterministic conversion the description adds the domain scope (which systems are accepted) but nothing about accuracy, rounding, or output behavior. That is a modest contribution above the annotations, not a rich one.

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?

The first sentence is front-loaded and specific about purpose with zero waste. The second sentence is a promotional URL for other APIs, which does not help an agent select or invoke the tool and is arguably noise, but it is clearly separable from the functional content.

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 simple two-parameter, no-output-schema conversion utility, the description names every supported system and matches the required inputs, which is enough to call it correctly. Missing are only edge details such as rounding of converted values, which are minor for this complexity.

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 both parameters carry detailed descriptions, including fraction/comma formats for `size` and the system meanings for `from`. The description's list of systems roughly mirrors the `from` enum, so it adds little meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ("Convert a hat size") plus the full set of supported systems: US fitted, UK, EU centimeters, inches, and S/M/L letters. This clearly separates it from siblings such as convert_clothing_size, convert_shoe_size, and convert_ring_size without needing to open any schema.

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 by the domain scope — an agent can infer this is the tool for hat sizes rather than shoes or clothing, but there is no explicit when/when-not statement and no named alternative such as size_chart or size_systems for chart lookups. Adequate but leaves routing to inference.

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