Skip to main content
Glama
io.github.mohammad-abbasi-sh/autobahn-mcp

io.github.mohammad-abbasi-sh/autobahn-mcp

autobahn_ev_charging

Find EV charging stations along a chosen German motorway, with a configurable result limit for trip planning.

Instructions

EV charging stations on one German motorway. road: e.g. "A1" or "A7". limit: 1..50 (default 10).

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

Input Schema

NameRequiredDescriptionDefault
roadNoA1
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does not state that the call is read-only, whether results are paginated, or how a valid road code is validated. The "one motorway" scoping constraint is the only behavioral fact offered, which is thin for an unannotated tool.

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

Conciseness4/5

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

Two short lines, purpose first and parameters second, with no filler. The telegraphic style is dense but every phrase carries information the agent needs.

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?

For a two-parameter read tool whose output schema already documents return values, the definition covers purpose and both parameters adequately. It leaves unclear what happens with an invalid or non-German road code, so it is viable but not fully complete.

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?

Schema coverage is 0%, so the description has to compensate, and it does: it documents the road format with two concrete examples ("A1", "A7") and the limit's range and default (1..50, default 10). It omits that road itself defaults to "A1" and whether road is case-sensitive, so it falls just short of full coverage.

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?

"EV charging stations on one German motorway" gives a specific resource and a clear scope, which separates it cleanly from siblings like autobahn_parking or autobahn_roadworks by domain. It stops short of an explicit verb such as "list", but the intent is unambiguous.

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 phrase "on one German motorway" implicitly tells the agent this is a per-road query, but there is no statement of when to prefer it over the sibling tools or any precondition. Usage is inferable from the resource name rather than explained.

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