Skip to main content
Glama

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

Decode a tire size

decode_tire_size
Read-onlyIdempotent

What does a tire size like 225/45R17 94W XL mean? Width, aspect ratio, construction, rim, diameter, load index and speed rating decoded. 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>"
    },
    "name": "decode_tire_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYesThe size as printed: "225/60R16 98H", "P225/60R16 97S", "LT265/70R17 121/118S E", "33x12.50R15 108Q", "7.50R16LT", "205/65R16C 107/105T". URL-encode the slash and spaces.

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 and closed-world, so the safety profile is covered elsewhere. The description adds that the result is a field-by-field breakdown rather than a single value, but says nothing about behavior on malformed or unsupported size formats, which is the main failure mode for a string parser.

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 core is tightly front-loaded: a leading question followed by an enumerated list of decoded fields, which is easy to scan. The trailing 'More APIs from FitzTopPicks' promotional URL with UTM parameters earns no place in a tool definition and drags the score down from a 5.

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 one-parameter read-only tool with no output schema, the enumerated field list usefully previews the return shape. However, since no output schema exists, the description would ideally confirm whether values are returned as labeled key/value pairs or a parsed string, and it omits any error behavior for invalid sizes.

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 explains the parameter thoroughly, including six accepted formats and the URL-encoding requirement. The description only restates one of those examples and adds no format or normalization guidance beyond the schema, so the baseline 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 uses a concrete example ('225/45R17 94W XL') and enumerates exactly what gets decoded: width, aspect ratio, construction, rim, diameter, load index and speed rating. That makes the verb+resource unmistakable, though it never contrasts itself with siblings like tire_load_index or tire_speed_rating that cover overlapping sub-fields.

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 rhetorical question 'What does a tire size ... mean?' – an agent can infer you call it to interpret a size string. There is no explicit when-to-use, no exclusions, and no pointer to compare_tire_sizes or the single-attribute siblings, so routing between them is left 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