Skip to main content
Glama

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

Convert a ring size

convert_ring_size
Read-onlyIdempotent

Convert a ring size between US, UK letters, EU/ISO, Japan and others, with the inside diameter and circumference. 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_ring_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe ring size system.
sizeYesThe size as written on the label or chart. Numbers take decimals, commas or fractions ("9.5", "9,5", "9½", "9 1/2", "N½" or "N 1/2" for UK letters, "Z+2").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety needs no restating. The description adds value by disclosing the response content (inside diameter and circumference), which matters because there is no output schema. It says nothing about behavior on unparseable input, which keeps it short of a 5.

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 second is a promotional blurb with UTM-tagged marketing URL that carries zero task value for an agent. Roughly half the text is wasted on self-promotion.

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?

With two fully described parameters, complete annotations, and no output schema, the description covers what is needed: what converts, from which systems, and that diameter/circumference come back. Only error/rounding behavior for malformed sizes is left unstated.

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% and both parameters are documented with examples, so the baseline is 3. The description reinforces that 'from' spans multiple systems including letter-based UK sizes, but adds no format or edge-case detail beyond the schema.

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?

Names a specific verb and resource ('Convert a ring size') plus the concrete scope: the size systems covered (US, UK letters, EU/ISO, Japan) and the derived measurements returned. An agent can immediately distinguish it from convert_hat_size, convert_shoe_size, and convert_clothing_size.

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 name and the listing of systems; there is no explicit statement of when to pick this over a sibling or which system to pass as 'from'. In practice the domain is narrow enough that an agent will rarely misfire, but no routing guidance is offered.

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