Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-wheel-size

by AIWerk
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

search-modifications-by-rim

Read-only

Find trim and modification variants of a known vehicle that are compatible with a given rim spec. Input make, model, and bolt pattern; refine with rim dimensions, offset, or centre bore.

Instructions

Find specific trim/modification variants of a known make+model that are compatible with a given rim spec. Required: make, model, bolt_pattern. Optional: rim dimensions, offset, centre bore, region. More granular than search-by-rim. Use when you already know the vehicle and want to check trim-level fitment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cbNoCentre bore diameter in mm (e.g. 66.5). Must be positive. Do not combine with cb_min/cb_max.
makeYesManufacturer slug (e.g. "audi"). Get slugs from list-makes.
limitNoMaximum results to return (1-100). Defaults to API default when omitted.
modelYesModel slug (e.g. "a4"). Get slugs from list-models.
cb_maxNoMaximum centre bore in mm. Must be positive. Use instead of cb for a range query.
cb_minNoMinimum centre bore in mm. Must be positive. Use instead of cb for a range query.
offsetNoNumber of results to skip for pagination.
regionNoMarket region code (e.g. "eudm", "usdm"). Get codes from list-regions.
rim_widthNoRim width in inches from bead seat to bead seat (e.g. 8.0). Must be positive.
rim_offsetNoExact rim offset (ET) in mm, range -100 to 100 (e.g. 35). The distance between the wheel mounting surface and the centre-line of the rim. Do not combine with rim_offset_min/rim_offset_max.
bolt_patternYesBolt pattern (PCD) expressed as stud-count × circle-diameter in mm (e.g. "5x112", "4x100"). Required. Use list-rim-bolt-patterns to enumerate valid values.
rim_diameterNoRim diameter in inches (e.g. 18). Must be positive. Filters results to this diameter only.
rim_width_maxNoMaximum rim width in inches. Must be positive. Use instead of rim_width for a range query.
rim_width_minNoMinimum rim width in inches. Must be positive. Use instead of rim_width for a range query.
rim_offset_maxNoMaximum rim offset (ET) in mm, range -100 to 100. Use instead of rim_offset for a range query.
rim_offset_minNoMinimum rim offset (ET) in mm, range -100 to 100. Use instead of rim_offset for a range query.
rim_diameter_maxNoMaximum rim diameter in inches. Must be positive. Use instead of rim_diameter for a range query.
rim_diameter_minNoMinimum rim diameter in inches. Must be positive. Use instead of rim_diameter for a range query.

Tool Definition Quality

A4.2/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, so the safety profile is covered. The description adds no additional behavioral details such as pagination, return format, or rate limits, which is acceptable given the annotation coverage but adds no extra context.

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 two sentences, with the core purpose front-loaded in the first sentence and usage context in the second. Every sentence serves a purpose with no filler.

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 complex 18-parameter search tool, the description provides a clear high-level purpose and when-to-use instructions. However, without an output schema, it does not describe what the results contain, which would enhance completeness but is not critical for tool selection.

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?

The input schema has 100% coverage with detailed descriptions for all 18 parameters, including examples and constraints. The description only restates required parameters and optional categories, adding no semantic value beyond the schema.

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 explicitly states it finds specific trim/modification variants for a known make+model compatible with a given rim spec, using the specific verb 'Find'. It clearly distinguishes from the sibling 'search-by-rim' by noting it is 'More granular than search-by-rim'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides direct when-to-use guidance: 'Use when you already know the vehicle and want to check trim-level fitment.' It also names the closest alternative, 'search-by-rim', with a comparative relationship, making the choice clear.

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