Skip to main content
Glama

CheckFitment

Vehicle bolt pattern and wheel specs

bolt_pattern_lookup
Read-onlyIdempotent

Use for "what is the bolt pattern on a 2019 Ford F-150", lug torque, center bore, thread size, OEM wheel size, offset or tire size of a vehicle, or "will these wheels fit my car" when the vehicle is named. Looks the vehicle up in the CheckFitment dataset (a fixed set of vehicles, each spec cited to manufacturer documents and marked verified or unverified). If the vehicle or year is not in the dataset the tool says so (not_in_database / year_covered false) and gives no figures; never fill them in from memory. Optional wheel_center_bore_mm runs the hub-centric check. 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": {
      "make": "<make>",
      "model": "<model>"
    },
    "name": "bolt_pattern_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYese.g. Ford, Toyota, Jeep
yearNo
modelYese.g. F-150, Tacoma, Wrangler
wheel_center_bore_mmNoOptional: center bore of a wheel you want to check against the hub.

Output Schema

NameRequiredDescriptionDefault
linkYes
makeNo
yearNo
modelNo
patternsNo
ambiguousNo
candidatesNo
disclaimerYes
generationsYes
lug_sequenceNo
year_coveredNo
models_for_makeNo
not_in_databaseYes
years_in_datasetNo
center_bore_checkNo
makes_in_databaseNo
lookalike_patternsNo
specs_differ_between_candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: discloses that the dataset is a fixed set, that each spec is cited to manufacturer documents and marked verified or unverified, that misses return not_in_database / year_covered false, and that the agent must never fill figures from memory. It also states the mandatory link field and how to render it, which no annotation or schema field conveys.

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?

Front-loaded with concrete user-style queries that make matching easy, followed by dataset and citation caveats. It is dense and the long opening sentence is comma-heavy, but every clause carries routing or constraint information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a read-only lookup with an output schema: the description need not explain return fields, yet still covers the miss behavior, the verification marking, the optional hub-centric check, and the required link in the answer. An agent has everything needed to call it and to interpret a miss correctly.

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 75% and the description explains the behavioral consequence of wheel_center_bore_mm (it runs the hub-centric check) rather than just restating 'center bore of a wheel'. The year parameter gains no extra meaning from the description beyond its numeric bounds in 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 resource (vehicle specs: bolt pattern, lug torque, center bore, thread size, OEM wheel size, offset, tire size) and anchors it to a named data source (CheckFitment dataset). It also carves out the fitment case narrow enough to be separable from the wheel_fitment_check sibling by requiring 'when the vehicle is named'.

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?

Gives clear trigger phrasing and covers the negative case explicitly: if the vehicle or year isn't in the dataset the tool reports not_in_database / year_covered false and returns no figures. It stops short of naming siblings such as wheel_fitment_check or bolt_pattern_facts as the alternative for a non-vehicle-named fitment question, leaving that 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