Skip to main content
Glama

CheckFitment

Tire size change: diameter and speedometer

tire_size_compare
Read-onlyIdempotent

Use for "what changes if I go from 265/70R17 to 285/75R17", "how far off is my speedometer with 33s", or odometer error after a tire change. Returns diameter, width, sidewall and ride-height change, the true speed when the speedometer shows a given value, the odometer error and how serious it is. Every result carries a link field: end the answer with that link as a markdown link, as the source page with the full citations.

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": {
      "old_tire": "<old_tire>",
      "new_tire": "<new_tire>"
    },
    "name": "tire_size_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_tireYesNew tire. Metric like 265/70R17 (P or LT prefix allowed) or flotation like 33x12.50R17; no load index or speed rating.
old_tireYesFactory or current tire. Metric like 265/70R17 (P or LT prefix allowed) or flotation like 33x12.50R17; no load index or speed rating.
speed_shownNoSpeedometer reading to convert (default 60).

Output Schema

NameRequiredDescriptionDefault
linkYes
new_tireYes
old_tireYes
severityYes
disclaimerYes
speed_shownNo
severity_noteNo
width_change_mmNo
diameter_change_inNo
odometer_error_pctNo
diameter_change_pctYes
true_speed_at_shownYes
ride_height_change_inNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds value beyond that by disclosing the shape of the results (diameter, sidewall, ride-height change, true speed, odometer error, severity) and a behavioral constraint on how to present the returned link field. It does not cover edge cases like invalid or incompatible tire formats, keeping it below 5.

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 description is front-loaded with "Use for" scenarios followed by the return summary and the link-presentation instruction, and no sentence is filler. It is slightly dense in a single paragraph, but every clause serves either routing or output-handling purposes.

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?

Given an output schema exists, the description needn't spell out return values, yet it summarizes them usefully and adds the non-obvious instruction to end answers with the link field as a markdown citation. It is essentially complete for a deterministic calculator; only error or incompatibility handling is unaddressed.

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%, so the schema already documents old_tire/new_tire formats and the speed_shown default of 60. The description's examples reinforce the accepted metric format and clarify that speed_shown is the speedometer reading to convert, adding modest meaning but not going beyond the schema in any substantive way, so the 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?

The description opens with concrete verb-and-resource intent tied to real queries ("what changes if I go from 265/70R17 to 285/75R17", "how far off is my speedometer with 33s") and then enumerates the outputs: diameter, width, sidewall, ride-height change, true speed, and odometer error. This makes it clearly a tire-size comparison calculator, distinct from siblings like wheel_fitment_check or gear_ratio_calculator.

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?

Usage is clear through the quoted example scenarios (size change, speedometer error, odometer error after a change), which tell an agent exactly the kind of question this tool answers. It stops short of naming alternatives or stating when another sibling tool (e.g., wheel_fitment_check for clearance) is preferable, so it lands at 4 rather than 5.

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