Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-wheel-size

by AIWerk

search-classified-rims

Read-only

Find aftermarket rims that fit your vehicle by specifying bolt pattern, diameter, width, and offset, and get compatibility-matched listings.

Instructions

Search aftermarket rim products by fitment spec, returning vehicle compatibility info alongside the rim listings. Required: bolt_pattern, rim_diameter (inches), rim_width (inches), rim_offset (ET mm). Optional: cb, fd, fitment tolerances, diameter_range, sort, limit, offset. Similar to list-classified-rims but includes vehicle-fitment matching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cbNoCentre bore diameter in mm (e.g. 66.5). Must be positive. Narrows results to matching bore size.
fdNoFastener thread diameter in mm. Must be positive. Filters by lug-bolt thread size.
sortNoSort order: "name" (A-Z by make/model), "fitment" (closest frontspace delta), "load" (heaviest first).
limitNoMaximum results to return (1-100).
offsetNoNumber of results to skip for pagination.
bs_pushNoBackspace push tolerance in mm (default 2). 0 = exact or safer only, no inward encroachment. Positive values allow more clearance margin.
fs_pokeNoFrontspace poke tolerance in mm (default 2). 0 = exact or safer only, no stick-out past the fender. Positive values allow increasing amounts of wheel poke.
rim_widthYesRim width in inches from bead seat to bead seat (e.g. 8.0). Required. Must be positive.
rim_offsetYesRim offset (ET) in mm, range -100 to 100 (e.g. 35). Distance from mounting face to rim centre-line. Required.
bolt_patternYesBolt pattern (PCD) as stud-count × circle-diameter in mm (e.g. "5x112", "4x100"). Required. Use list-rim-bolt-patterns to enumerate valid values.
od_toleranceNoOverall diameter tolerance as a decimal fraction (0-0.05, default 0.01 = 1%). Controls how closely the product OD must match the vehicle spec.
ow_toleranceNoOverall width tolerance as a decimal fraction (0-0.03, default 0).
rim_diameterYesRim diameter in inches (e.g. 18). Required. Must be positive.
diameter_rangeNoWiden rim diameter search by ±N inches, min 0 (default 0 = exact match only). E.g. diameterRange=1 on an 18-inch search also returns 17 and 19-inch options.
Behavior4/5

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

Annotations convey read-only and open-world. Description adds behavioral context: returns vehicle compatibility info, focuses on fitment spec search. This extends beyond annotations, though no rate-limit or pagination notes.

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?

Two sentences with clear front-loaded purpose. Minor redundancy with schema in listing params, but overall efficient and readable.

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?

For a 14-param tool with no output schema, description covers purpose, differentiator, and parameter categories. Could include an example or default behaviors, but sufficient.

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 baseline 3. Description only restates required/optional param names, adding no new semantics beyond schema. Thus no uplift.

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?

Specific verb+resource: 'Search aftermarket rim products by fitment spec'. Explicitly distinguishes from sibling: 'Similar to list-classified-rims but includes vehicle-fitment matching.' This leaves no ambiguity about what the tool does.

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?

Names alternative tool (list-classified-rims) and explains the difference (vehicle-fitment matching). Lists required parameters, but no explicit exclusion of when not to use. That said, the sibling comparison is enough to guide selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIWerk/mcp-server-wheel-size'

If you have feedback or need assistance with the MCP directory API, please join our Discord server