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

io.github.sergioprats/pitwall-mcp

by sergioprats
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Buscar descriptores telematicos

search_descriptors
Read-onlyIdempotent

Search the local BMW CarData catalog to identify available descriptors. Accepts Spanish or English queries without consuming API quota.

Instructions

Busca en el catalogo telematico local de BMW CarData (294 descriptores). Acepta consultas en espanol o en ingles. NO gasta cuota de la API: el catalogo es un fichero local. Es la unica fuente de verdad sobre que descriptores existen.

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": {
      "query": "<query>"
    },
    "name": "search_descriptors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
include_electricNo

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 declare readOnly/idempotent/destructive hints. The description adds important non-obvious behavior: the catalog is a local file, has 294 entries, does not spend API quota, and accepts Spanish or English input. This goes beyond the annotations without contradicting them.

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 short, focused sentences with no filler. The main purpose is front-loaded, followed by high-value operational details such as API quota usage and language support.

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?

The description covers purpose, local scope, quota behavior, and the catalog as source of truth, and the output schema handles return values. However, with no parameter descriptions in the schema and 0% coverage, the missing explanation of limit and include_electric leaves the tool incompletely specified.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only clarifies that queries may be in Spanish or English. It does not explain the semantics of 'limit' or 'include_electric', which are not self-evident from the schema alone.

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 names a specific verb and resource: 'Busca en el catalogo telematico local de BMW CarData (294 descriptores).' It also clearly states the tool is the 'unica fuente de verdad' for which descriptors exist, which distinguishes it from sibling data-retrieval tools.

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 clear context on when to use the tool: it searches a local catalog, accepts Spanish/English queries, and does not consume API quota. It does not explicitly name alternatives or exclusions, but it makes the intended use obvious.

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