@aiwerk/mcp-server-wheel-size

wheel-upsteps

Read-only

Suggest aftermarket wheel upsize options that keep tire diameter within tolerance. Returns PCD, offset, centre bore, and tire specs to preserve speedometer accuracy.

Instructions

Get aftermarket wheel upsize (plus-sizing) suggestions for a vehicle. Returns larger rim diameter options that maintain overall tyre diameter within acceptable tolerance. Key fitment terms returned: PCD (bolt pattern), offset (ET in mm), centre bore (CB in mm), section width, aspect ratio. Use this to recommend wheel upgrades while preserving speedometer accuracy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "make": "<make>",
      "model": "<model>",
      "year": "<year>",
      "region": "<region>"
    },
    "name": "wheel-upsteps"
  }
}

Input Schema

Name	Required	Description
`make`	Yes	Manufacturer slug from list-makes (e.g., "audi", "ford").
`year`	Yes	4-digit model year 1900-2100 (e.g., 2020).
`model`	Yes	Model slug from list-models (e.g., "a4", "f-150").
`region`	Yes	Market code from list-regions (e.g., "usdm", "eudm"). Upstep suggestions are region-specific due to different OEM baseline specs. Key fitment terms: PCD (bolt pattern, e.g., 5x112), offset (ET value in mm), centre bore (CB in mm), tyre section width and aspect ratio.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Aug 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description discloses that suggestions maintain overall tyre diameter within 'acceptable tolerance' and includes the set of returned fitment terms, which goes beyond the read-only annotation. It does not quantify the tolerance or cover error conditions, but with annotation coverage that's a reasonable level of detail.

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?

Three direct sentences, with the main action and scope in the first sentence and no filler. The usage note is valuable and the fitment-term list is compact.

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?

Despite no output schema, the description explains both what is returned (fitment terms) and the constraint it satisfies. It is sufficient for an agent to select and invoke the tool, though it lacks details on failure modes or data availability.

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?

All four parameters are fully described in the schema with examples and constraints, so the 100% coverage baseline applies. The description adds context about region-specific suggestions and key fitment terms, but does not materially extend parameter semantics.

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 opens with a specific verb and object: 'Get aftermarket wheel upsize suggestions', and clarifies scope by naming the returned fitment terms. This clearly differentiates it from sibling list/search tools by focusing on plus-sizing recommendations rather than raw data lookup.

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 final sentence explicitly says 'Use this to recommend wheel upgrades while preserving speedometer accuracy', providing a clear use case. However, it doesn't name alternatives or explicitly state when not to use it, so it stops short of full differentiation.

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