Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-wheel-size

by AIWerk
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

search-modifications-by-classified-rim

Read-only

Find aftermarket rims compatible with a specific vehicle by matching bolt pattern, rim diameter, width, and offset to make, model, and generation.

Instructions

Find aftermarket rim products compatible with a specific vehicle make/model/generation. Required: bolt_pattern, rim_diameter, rim_width, rim_offset, make, model, generation. Optional: cb, fd, fitment tolerances, diameter_range, sort, limit, offset.

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.
makeYesManufacturer slug (e.g. "audi"). Get slugs from list-makes.
sortNoSort order: "name" (A-Z by make/model), "fitment" (closest frontspace delta), "load" (heaviest first).
limitNoMaximum results to return (1-100).
modelYesModel slug (e.g. "a4"). Get slugs from list-models.
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.
generationYesGeneration slug (e.g. "b9"). Get slugs from list-generations.
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.

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, providing the core safety profile. The description adds no further behavioral context such as pagination, rate limits, result shape, or external data dependencies. It goes beyond annotations only by clarifying the vehicle compatibility scope, but that is more purpose than behavior.

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 a single sentence that front-loads the main action and scope. It efficiently lists required and optional parameters, though the list is long and could be better structured. Overall it is concise and earns its place without fluff.

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?

With no output schema, the description should ideally convey return value expectations or pagination behavior; it does not. However, it clearly covers the tool's purpose and required inputs, which is adequate for a search tool with 17 parameters, but lacks completeness around response format and operational details.

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 baseline is 3. The description only restates the required/optional parameters without adding new semantic details; all meaningful parameter explanations are already in the schema.

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 clearly states the tool finds aftermarket rim products compatible with a specific vehicle make/model/generation, which is a specific verb+resource+scope. It implicitly differentiates from sibling search-modifications-by-rim by requiring vehicle details (make/model/generation) plus rim specs, though it does not explicitly name alternatives.

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?

The description lists required and optional parameters, implying the tool should be used when those details are available for a vehicle-specific rim search. However, it does not provide explicit when-to-use versus when-not-to-use guidance or name alternative sibling tools for other search scenarios.

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