Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-wheel-size

by AIWerk
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

list-classified-rims

Read-only

Find aftermarket rims that fit your bolt pattern, diameter, width, and offset. Returns compatible product listings with SKU data.

Instructions

List aftermarket rim products compatible with a given rim fitment spec. Required: bolt_pattern, rim_diameter (inches), rim_width (inches), rim_offset (ET mm). Optional: cb, fd, fitment tolerances (fs_poke, bs_push, od_tolerance, ow_tolerance), diameter_range, sort, limit, offset. Returns rim product listings with SKU data.

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.

Tool Definition Quality

A4/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, covering safety and open-world assumptions. The description adds that it returns 'rim product listings with SKU data' and notes fitment tolerances, but does not disclose behavioral details like default sort or pagination beyond what the schema already provides. No contradiction.

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?

The description is a single, information-dense sentence that front-loads the main action and then systematically lists required and optional parameters. There is no wasted language; every part contributes to understanding what the tool does and what to pass.

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?

With 14 parameters and no output schema, the description names all required and optional inputs and states the high-level return type. It does not differentiate from the sibling search-classified-rims tool or clarify the 'classified' aspect, but given the rich schema and overall clarity, it is largely complete for practical invocation.

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 each parameter is already fully documented. The description adds a high-level summary of required vs optional and groups tolerance parameters, but this is a redundant overview rather than new semantic meaning. 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?

The description clearly states the tool's purpose with a specific verb ('List') and resource ('aftermarket rim products'), scoped by 'compatible with a given rim fitment spec.' It distinguishes itself from sibling list tools that enumerate individual parameters (e.g., list-rim-diameters, list-rim-bolt-patterns) by focusing on product listings.

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?

The description explicitly lists required and optional parameters, making it clear the tool is used when a fitment spec is known and compatible rim products are needed. It does not mention alternatives or when not to use it, but the context is clear 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