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

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

autobahn_health

Checks whether verkehr.autobahn.de is reachable now and returns ok, blocked, or error status with the HTTP code and probed URL, using one polite request without fetching listings.

Instructions

Check whether verkehr.autobahn.de is reachable right now.

Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings.

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_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden, and it discloses the three outcome classes with their HTTP meanings: ok for 200, blocked for 403/429 due to a bot wall or rate limit, and error. It also states that it returns the HTTP status and probed URL, and that it makes one polite request without fetching listings.

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?

The description is front-loaded with the action, then explains return statuses, then states the side-effect scope. Every sentence adds useful information and nothing is repeated from schema fields.

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

Completeness5/5

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

For a simple zero-parameter health check with an output schema, the description covers purpose, outcomes, side effects, and scope. No material detail needed to invoke it correctly is missing.

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?

There are zero input parameters, so the baseline is 4; the description appropriately adds no parameter semantics because none exist. Its return-value details are useful context but are not parameter semantics.

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?

The description uses a specific verb, 'Check', and a specific resource, 'verkehr.autobahn.de reachability right now', and explicitly distinguishes this from listing-fetching siblings by saying it 'does not fetch any listings'. An agent can identify it as a diagnostic health check 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The diagnostic context is clear from 'reachable right now' and the statement that it does not fetch listings, which rules out use as a data-retrieval tool. However, it does not name a specific sibling alternative or state an explicit fallback workflow, so guidance is clear but not exhaustive.

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