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

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

autobahn_closures

Retrieve current closures on a specified German motorway such as A1, with a configurable result limit for focused traffic updates.

Instructions

Closures on one German motorway. road: e.g. "A1" or "A100". 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_closures"
  }
}

Input Schema

NameRequiredDescriptionDefault
roadNoA1
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does little: it never says whether results are current/planned closures, whether they are real-time or scheduled, whether the query is read-only or what the response shape is. Only the limit bound (1..50) is disclosed as behavioral constraint, which is minimal for a tool with zero annotation coverage.

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 sentences with the purpose front-loaded and zero filler; the parameter notes are telegraphic but readable. The colon-separated parameter list is efficient rather than padded.

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 described, and the tool is simple with two optional parameters. Still, a lookup tool with no annotations and no statement of data freshness or coverage (which motorways, current vs. planned) leaves an agent guessing about result reliability.

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 for both parameters: it gives concrete road identifier format examples ("A1", "A100") that the schema does not, and it supplies the undocumented limit range 1..50 plus the default. It could still note the road default or whether the road is optional, but the essential semantics are present.

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?

"Closures on one German motorway" names the resource (motorway closures) and scopes it geographically, which is enough to distinguish it from the sibling autobahn_* tools that cover EV charging, health, parking, roadworks and warnings. It stops short of an explicit comparative statement, so it lands at 4 rather than 5.

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 when-to-use guidance, no mention of when not to use it, and no explicit alternative (e.g. roadworks vs. warnings vs. closures) despite five closely related siblings. The agent must infer from the names alone which autobahn_* endpoint answers its question.

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