io.github.sergioprats/pitwall-mcp

Overview Schema Source Related Servers Discussions Admin

Estado del vehiculo: kilometraje y CBS

get_vehicle_status

Read-onlyIdempotent

Retrieve current mileage and Condition Based Service (CBS) maintenance alerts from BMW CarData to identify when service is due.

Instructions

Kilometraje y avisos de mantenimiento (CBS). El desglose CBS por partida esta pendiente de verificar contra una respuesta real: la estructura de El desglose por partida esta verificado contra una respuesta real.

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": "get_vehicle_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description attempts to add a verification caveat about the CBS breakdown, but the phrasing is self-contradictory ('pendiente de verificar' vs 'verificado'), leaving the data trustworthiness unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is concise and useful, but the second sentence is garbled, repetitive, and internally contradictory. It does not earn its place and undermines the overall clarity of the description.

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 zero parameters, a full output schema, and safety annotations, the description only needs to clarify purpose and data caveats. It conveys the core purpose but the confusing verification statement leaves important ambiguity about the reliability of the CBS breakdown.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so parameter semantics are not a concern. The baseline of 4 applies because there is nothing the description needs to add beyond what the empty schema already indicates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource and payload: mileage and CBS maintenance reminders. It is not a tautology and conveys a specific read operation, although it does not explicitly differentiate this tool from get_maintenance_summary or other vehicle-data siblings.

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

Usage Guidelines2/5

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

The description provides no guidance about when to use this tool instead of siblings such as get_vehicle_basic_data, get_maintenance_summary, or get_fuel_status. No alternatives, selection criteria, or exclusions are mentioned.

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

Deploy Server