Skip to main content
Glama

CheckFitment

Bolt pattern in mm and inches, look-alikes

bolt_pattern_facts
Read-onlyIdempotent

Use for "what is 5x114.3 in inches", "is 5x114.3 the same as 5x115", "will 6x135 wheels fit 6x139.7", or which vehicles use a pattern. Converts mm and inch notation, lists look-alike patterns that do not interchange, the vehicles in the dataset with that pattern, the lug tightening order and typical torque ranges by stud size (guidance only). 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": {
      "pattern": "<pattern>"
    },
    "name": "bolt_pattern_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYes5x114.3, 5x4.5, 6x139.7, 8x6.5 …

Output Schema

NameRequiredDescriptionDefault
linkYes
lugsYes
pcd_inNo
pcd_mmNo
disclaimerYes
lookalikesYes
pattern_inYes
pattern_mmYes
lug_sequenceNo
vehicles_in_datasetYes
typical_torque_by_studNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description adds real value beyond them: it discloses that torque figures are 'guidance only' and that every result carries a 'link' field that must be surfaced as a markdown citation. It stops short of describing pagination or dataset scope limits.

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?

Use cases are front-loaded in a single dense sentence followed by output content and the citation instruction. Every clause carries information, though the middle sentence is a long run-on list that could be split for scanability.

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?

An output schema exists, so return values need not be spelled out, yet the description still flags the one output field that affects answer formatting (the mandatory citation link). With annotations covering safety and the single parameter fully documented, nothing an agent needs to call this correctly is missing.

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?

There is a single required parameter with 100% schema description coverage, so the schema already supplies the accepted notation examples. The description only reinforces that both mm and inch notation are accepted, which is marginal added meaning. Baseline 3 is appropriate.

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 specific operations: mm/inch conversion, look-alike pattern listing, vehicle enumeration, and lug order/torque guidance. It is clearly more than a restatement of the name. It does not, however, differentiate itself from the close sibling bolt_pattern_lookup, so an agent cannot tell from the description alone which of the two to pick.

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?

It gives concrete trigger queries — 'what is 5x114.3 in inches', 'is 5x114.3 the same as 5x115', 'will 6x135 wheels fit 6x139.7' — which effectively communicate when to use it. There are no explicit exclusions or named alternatives such as wheel_fitment_check or bolt_pattern_lookup, so the routing decision is only partly covered.

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