Skip to main content
Glama
Sign In
io.github.sergioprats/pitwall-mcp

io.github.sergioprats/pitwall-mcp

by sergioprats
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Resumen de mantenimiento

get_maintenance_summary
Read-onlyIdempotent

Obtain a ready-to-paste BMW maintenance summary: mileage, CBS service intervals, tire pressures vs targets, and oldest data date.

Instructions

Bloque de texto listo para pegar en un prompt: kilometraje, partidas CBS con km y fecha restantes, presiones de las cuatro ruedas en bar contra su objetivo, y la fecha del dato mas antiguo utilizado.

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_maintenance_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond that: the output is a pre-formatted text block, pressures are compared against targets, and the result includes the date of the oldest data used, which signals data freshness. There is no contradiction with 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?

A single sentence front-loads the core purpose ('Bloque de texto listo para pegar en un prompt') and then uses a colon-delimited list to enumerate the exact contents. There is no filler or redundancy.

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 zero-parameter read-only tool, the description is complete: it names the output format, the specific data points included, units for tyre pressure, and a data-freshness qualifier. The presence of an output schema also reduces the need to explain return values further.

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 and the schema shows 100% coverage by having no properties. With no parameters to document, the baseline is 4; the description does not need to explain argument semantics.

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 states the tool returns a ready-to-paste text block containing maintenance information: mileage, CBS items with remaining km and date, tyre pressures in bar versus targets, and the age of the oldest data used. This is a specific resource plus an explicit deliverable, though it does not explicitly contrast itself with sibling tools like get_vehicle_status or get_tyre_diagnosis.

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

Usage Guidelines3/5

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

The description implies usage when a copy-paste maintenance summary is needed and even mentions the intended use in a prompt, but it gives no explicit when-to-use versus alternatives, no exclusions, and no guidance about overlapping sibling tools. The usage context is only implicit.

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