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

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

autobahn_parking

Find truck and car parking areas on a German motorway, including capacities. Query by road such as A1 or A7 and set a result limit to plan rest stops.

Instructions

Truck/car parking areas on one German motorway, with capacities. 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_parking"
  }
}

Input Schema

NameRequiredDescriptionDefault
roadNoA1
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does signal this is a capacity lookup (read-style, low risk) and gives a default and range for limit, which hints at result-size behavior. It does not disclose pagination, whether results are sorted, or what happens for an unknown road code.

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

Conciseness3/5

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

It is short and front-loads the purpose, so nothing is wasted. However, the parameter notes are crammed into the same sentence and written in a clipped schema-comment style ('road: e.g. "A1" or "A7". limit: 1..50'), which reads more like a fragment than a structured 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?

An output schema exists, so return values need not be explained, and both parameters are covered. For a two-parameter lookup this is close to adequate, but the missing usage guidance and error behavior for an invalid motorway leave a small gap.

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 description coverage is 0%, so the description must compensate, and it does: 'road' gets concrete examples ('A1' or 'A7') and 'limit' gets a valid range (1..50) plus its default value of 10. That is meaningful added meaning over the bare schema, though it doesn't say whether road matching is exact or prefix-based.

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 names a specific resource ('Truck/car parking areas on one German motorway') and adds the qualifier 'with capacities', which tells the agent what the results contain. It doesn't explicitly contrast with siblings like autobahn_roadworks or autobahn_closures, but the resource noun is distinctive enough to disambiguate.

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?

There is no statement of when to use this versus the other autobahn tools, nor any precondition such as whether the road must be a valid motorway. The only implicit guidance is the 'one German motorway' scope, which the agent has to infer from the parameter hint.

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