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

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

autobahn_roadworks

Retrieve roadworks for a specified German Autobahn, such as A1 or A100, with an adjustable result limit. Use it to check construction zones and plan routes.

Instructions

Roadworks 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_roadworks"
  }
}

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
Behavior3/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; it discloses the default limit of 10 which hints at a bounded result set, and the tool is implicitly a read-only fetch. It does not state whether results are paginated, ordered, or how many roadworks typically come back, and no auth or rate-limit context is given. The presence of an output schema reduces the need to describe return values.

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 with the resource stated first and parameter hints second, with no filler. The fragmented phrasing ("road: e.g. ...") is terse but readable and front-loaded.

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 with an output schema, the essential parameter semantics are covered and nothing is misleading. However, with zero annotation coverage the description should at least confirm this is a read-only lookup and clarify the boundary against autobahn_closures, which it does not.

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: it gives a concrete format example for road ("A1" or "A100") and states the accepted range and default for limit (1..50, default 10). Only the default road value of "A1" is unexplained.

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 (roadworks) and scope (one German motorway), which distinguishes it in substance from siblings like autobahn_closures and autobahn_warnings even though it doesn't name them. An agent can tell what it returns without opening the schema.

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 guidance on when to choose this over autobahn_closures or autobahn_warnings, which is the key ambiguity since roadworks and closures overlap conceptually. Usage must be inferred entirely from the resource name.

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