boltpatternhq-mcp

search_bolt_pattern

Search automotive wheel fitment specifications including PCD, bolt pattern, center bore, offset, thread size, and lug count by vehicle make, model, year, or exact PCD.

Instructions

Search automotive wheel fitment specifications (PCD / bolt pattern, center bore, offset ET, thread size, lug count) by vehicle make, model, year, or exact PCD (e.g. 'Jimny', 'Roadster', '5x114.3', 'Raize', 'BMW 3 Series').

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": {
      "query": "<query>"
    },
    "name": "search_bolt_pattern"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search term: vehicle model name, manufacturer make, chassis code, or bolt pattern (e.g., 'Jimny', 'MX-5', '4x100', 'Tesla').

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 29, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so description must convey behavioral traits. It states it searches and gives examples, but does not mention pagination, response format, query limits, or behavior for invalid inputs. Given it's a read-only search tool, essential traits are partially covered but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with examples, no wasted words. Efficiently conveys tool purpose and input format.

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?

Given one required parameter and no output schema, the description covers the input but lacks details on output structure, expected result count, or error handling. For a simple search tool, it meets basic needs but could be more complete.

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 describes the single 'query' parameter with examples. Description adds context about what is searched (wheel fitment specs), but no additional parameter-specific meaning beyond the schema. Schema coverage is 100%, so baseline 3 is appropriate.

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?

Clear verb 'Search' with specific resource 'automotive wheel fitment specifications'. Lists the types of specifications (PCD, center bore, etc.) and search methods (by make, model, year, exact PCD). Distinct from siblings: get_make_models likely returns lists of models, and get_sample_data provides sample data, so this tool focuses on fitment search.

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?

No explicit guidance on when to use this tool versus alternatives like get_make_models. The description implies usage for searching fitments by vehicle details or patterns, but does not mention prerequisites or when this tool is preferred over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server