Skip to main content
Glama

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

Tire speed rating

tire_speed_rating
Read-onlyIdempotent

What top speed does a tire speed rating letter allow (e.g. H = 210 km/h), or which rating covers a speed? More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tire_speed_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomph (default) or kmh, with minSpeed.
symbolNoA speed symbol: A1-A8, B-Y, (Y) or ZR.
minSpeedNoSpeed to cover.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world lookup, so the safety profile is fully covered. The description adds the domain example (H = 210 km/h) and the dual-direction nature of the query, but says nothing about error behavior for an invalid symbol or about what the response looks like.

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 well front-loaded and does real work, packing both lookup directions into one line. The trailing 'More APIs from FitzTopPicks' URL is marketing noise that consumes roughly half the description without helping an agent select or call the tool.

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?

With no output schema, the description must imply return values; the H = 210 km/h example partially does that for the symbol direction but not for the minSpeed direction. It also leaves undefined what happens with zero arguments, which matters for a tool with all-optional parameters.

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 each parameter is documented, so the baseline of 3 applies. The description does clarify the either/or relationship between symbol and minSpeed+unit that the schema only hints at, but adds no format detail, valid symbol range, or unit defaults beyond what the schema already states.

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 names the exact resource (tire speed rating letters) and states both directions of lookup: symbol to top speed, and speed to covering rating, with a concrete example (H = 210 km/h). It is clearly a different resource than siblings like tire_load_index or decode_tire_size, though it never names or contrasts them explicitly.

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

Usage Guidelines4/5

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

The two question forms in the description map cleanly onto the two usage modes: pass a symbol for a rating lookup, or pass minSpeed (+unit) for the inverse lookup. That is clear contextual guidance, but there are no explicit exclusions, no mention of what happens when neither or both are supplied, and no routing to sibling tools.

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