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

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

autobahn_warnings

Retrieve current warnings for a specified German motorway, with an optional limit, to check road issues and plan travel.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
roadNoA100
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden, and it discloses little: no read-only confirmation, no auth or rate-limit notes, no statement of whether results are live/current or how many records exist. The only behavioral hint is the limit cap of 1..50 with a default of 10, 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?

The text is short and front-loaded: the resource and scope come first, then per-parameter notes. The telegraphic "road: e.g." style is efficient, though slightly terse for a standalone definition.

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-shape explanation is not required, and for a two-parameter read tool the basics are covered. Still missing are what a warning represents, whether the data is current, and any behavioral constraints, which leaves the definition thinner than the tool's unannotated status warrants.

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

Parameters3/5

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

Schema description coverage is 0%, so the schema contributes only titles and defaults. The description does add real value by giving road format examples ("A100" or "A1") and an explicit 1..50 range with default for limit, but it never states what limit actually counts (warnings returned? pages?) or whether road accepts multiple values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Warnings on one German motorway" states the resource and narrows scope to a single road, but supplies no verb (list/get) and never distinguishes these warnings from the sibling datasets (closures, roadworks, parking). "Warnings" itself is left unqualified, so an agent must guess whether these are traffic, weather, or hazard warnings.

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 prerequisite or exclusion, and no mention of any sibling tool as an alternative. The description only implies usage through the scoping phrase "one German motorway," leaving the agent to infer the rest.

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