Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-wheel-size

by AIWerk

search-modifications-by-classified-package

Read-only

Search for wheel and tyre packages compatible with a specific vehicle make, model, and generation by entering bolt pattern, rim size, and offset specifications.

Instructions

Find wheel+tyre package products compatible with a specific vehicle make/model/generation. Required: bolt_pattern, rim_diameter, rim_width, rim_offset, section_width, aspect_ratio, make, model, generation. Optional: tolerance and fitment parameters (same as search-classified-packages). Use when you need to verify package compatibility for a particular trim level.

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.
aspect_ratioYesTyre aspect ratio as a percentage integer 1-100 (e.g. 45). 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.
section_widthYesTyre section width in mm (e.g. 245). 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.
Behavior3/5

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

Annotations already declare readOnlyHint=true, covering the read-only nature. The description adds that the tool requires vehicle make/model/generation and optional tolerance/fitment parameters, but it does not explain how compatibility is determined, what openWorldHint means, or potential edge cases. This adds some context but lacks deeper behavioral disclosure.

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 exactly two sentences, front-loaded with the core purpose, then listing requirements and usage. Every word earns its place; there is no fluff or redundancy.

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 the tool has 19 parameters and no output schema, the description covers the primary purpose and required parameters but omits return format, pagination behavior, and explanation of openWorldHint. It is minimally viable but leaves notable gaps for a high-complexity tool.

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?

With 100% schema description coverage, every parameter is already well-documented in the schema. The description merely lists the required parameters and points to search-classified-packages for optional ones, which does not add meaning beyond the schema. 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 'Find wheel+tyre package products compatible with a specific vehicle make/model/generation,' which pairs a specific verb with a defined resource and scoping criteria. It distinguishes this tool from siblings like search-modifications-by-rim or search-by-rim by focusing on wheel+tyre packages and requiring vehicle identifiers.

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 provides an explicit usage context: 'Use when you need to verify package compatibility for a particular trim level.' It also references search-classified-packages for optional parameter meanings, which is helpful. However, it does not explicitly state when not to use it or name alternatives for vehicle-less or single-component searches, leaving some room for ambiguity.

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