Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_autobahn_traffic_status

Fetch live traffic jams, roadworks, and closures on any German federal motorway (A1–A99) from Die Autobahn GmbH des Bundes.

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

Input Schema

NameRequiredDescriptionDefault
autobahnNoAutobahn identifier (e.g. A1, A2, A3, A7, A8, A9)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 behavioral burden; it usefully discloses that data is live and sourced from Die Autobahn GmbH, which signals real-time freshness. It does not address what happens when the optional autobahn parameter is omitted (all motorways vs. error), invalid identifiers, rate limits, or result size.

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

Conciseness5/5

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

A single front-loaded sentence naming verb, data types, scope, and source; nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with a fully described schema and no output schema, the description covers what is returned and the scope well. The only material gap is the unstated default behavior when the optional autobahn filter is not supplied.

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 100% and the single optional parameter is already documented with examples, so the schema does the heavy lifting and baseline applies. The description adds the A1–A99 range constraint and reinforces the parameter's domain, but does not clarify the omitted-parameter behavior.

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

Purpose5/5

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

States a specific verb (fetch), a precise resource (live traffic jams, roadworks, closures), and the bounded scope (German federal motorways A1–A99) with the data source named. No sibling covers traffic data, so it is trivially distinguishable within the catalog.

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?

Usage is only implied: an agent can infer this is the tool for current German motorway conditions because of the explicit resource and scope, but there is no statement of when to prefer it, no exclusions, and no alternative named for other regions or historical traffic data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources