Skip to main content
Glama
Sign In
@aiwerk/mcp-server-wheel-size

@aiwerk/mcp-server-wheel-size

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list-tire-section-widths

Read-only

List tyre section widths in millimeters, optionally filtered by region, to discover valid values for tire fitment searches.

Instructions

List all tyre section widths (in mm) available in the database, optionally filtered by region. Use this to discover valid section_width values for search-by-tire.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-tire-section-widths"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoMarket region code (e.g. "eudm", "usdm"). Get codes from list-regions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already include readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context beyond annotations, such as the unit (mm) and the optional region filtering, without contradicting the annotations.

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 no wasted words. The first states the core function, the second provides a specific use case, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter and no output schema, the description fully covers what the tool does, the unit of results, the filter option, and a concrete use case. It is complete within its complexity class.

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 parameter 'region' is fully documented in the schema. The description adds only marginal value by mentioning the optional region filter, matching the schema; this is the baseline 3 for high coverage.

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 lists all tyre section widths in mm, with an optional region filter. It also distinguishes itself by noting it is for discovering valid section_width values for search-by-tire, setting it apart from sibling list tools like list-tire-aspect-ratios.

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 provides explicit context for use ('Use this to discover valid section_width values for search-by-tire'), which is clear and actionable. However, it does not explicitly mention when not to use this tool or name alternatives, so it falls short of a 5.

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

Deploy Server

Other Tools