Skip to main content
Glama

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

Compare two tire sizes

compare_tire_sizes
Read-onlyIdempotent

Will a different tire size fit, and how does it change the speedometer? Diameter, width and sidewall differences and the speedometer error between two sizes. 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "compare_tire_sizes"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe new size.
fromYesThe original size.
unitNomph (default) or kmh.
speedNoSpeed shown on the speedometer (default 60 mph or 100 km/h).

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description adds that the operation is a comparative computation returning differences rather than a lookup, but says nothing about whether a fitment verdict is included, thresholds used, or error handling for unparseable sizes.

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 two substantive sentences are front-loaded and information-dense. However, the trailing 'More APIs from FitzTopPicks' promotional URL with UTM parameters is pure noise that dilutes an otherwise tight definition.

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?

There is no output schema, so the description must carry the return-value burden, and it does list the specific outputs computed (diameter, width, sidewall differences, speedometer error). What's missing is whether a boolean fitment verdict or clearance warnings are returned, which the opening question implies but never confirms.

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%, with from/to, the mph/kmh enum, and the speed default all documented in the schema itself. The description adds no parameter-level meaning — it never mentions units, the speed input, or the format expected for size strings — so 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 opens with a concrete question ('Will a different tire size fit, and how does it change the speedometer?') and enumerates the computed quantities (diameter, width, sidewall, speedometer error), so the verb+resource is unambiguous. It doesn't explicitly contrast itself with the sibling decode_tire_size (one size, not two), but the 'between two sizes' framing makes the distinction inferable.

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 implied through the fitment question, which tells an agent the tool answers 'will this swap work' scenarios. There is no explicit when-to-use vs. when-not statement and no named alternative (e.g., decode_tire_size for parsing a single size), leaving 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