Skip to main content
Glama
mavrovde

ViaFrei

by mavrovde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

check_transit_disruption

Read-onlyIdempotent

Get current public transport punctuality for a German region: share of trips delayed over 5 minutes, cancellations, and trend versus the previous period, to detect strike or storm disruption.

Instructions

Returns how punctual public transport is right now in one German region: the share of distinct trips more than 5 minutes late at least once, trips with a cancelled stop, the trend against the previous window, and how many trips that rests on. Use when the user asks whether buses and trains are running normally, or whether a strike or storm is disrupting local transport. Do NOT use for one line, trip or station — per-line realtime is not available; the region's figures are the answer. Region-wide aggregates only; window ≤ 120 minutes. CC BY-SA 4.0: show the attribution line to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude in WGS 84, e.g. 48.137. Use with lon when the caller already holds coordinates; otherwise use region.
lonNoLongitude in WGS 84, e.g. 11.576. Use with lat; otherwise use region.
regionNoThe German region to report on, as free text: a Bundesland ("Bayern", "Bavaria", "Nordrhein-Westfalen"), a city ("Hamburg", "Köln") or a Kreis ("Landkreis Fulda"). A town inside a Kreis is reported as that Kreis and the answer says so, because the data is filed at Kreis level. Not a stop, not a street, not an address. Give either region OR lat+lon, never both.
languageNoSet this on every call to the language the person is writing in: "en" if they wrote English, "de" if they wrote German. Do not leave it out because it has a default — the default is only the fallback when the language is genuinely unclear, and an English question answered in German is a wrong answer. Place names, station names and road numbers are never translated in either language; in English the German term is kept in parentheses so the person recognises it on signs and in local apps.de
window_minNoHow many minutes back to look, 5–120 (default 60). The trend compares this window with the equally long one before it, so 60 means "the last hour against the hour before". Use a short window for "right now" and a long one for "has it been bad all morning".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.9

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the readOnlyHint annotations: the exact lateness threshold (5 minutes), what counts as a cancelled stop, the trend comparison window, and the sample size. It also discloses the CC BY-SA 4.0 attribution requirement)Skip to user. These are meaningful operational details an agent would otherwise not know.

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 about four sentences and every sentence earns its place: what it returns, when to use it, when not to use it, and a required attribution. The most important scope and comparison details are front-loaded, with the licensing note cleanly at the end.

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?

With no output schema, the description sufficiently explains the returned information (punctuality share, cancelled stops, trend, trip count). The parameter schema covers invocation details, and the description fills the usage and exclusion gaps. Nothing essential is missing for an agent to decide and call it correctly.

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%, so the schema already fully documents lat, lon, region, language, and window_min. The description adds some reinforcing context (region-wide aggregates, window ≤ 120 minutes, trend interpretation) but does not materially expand parameter semantics beyond what the schema provides.

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 opens with a specific verb ('Returns') and names the exact resource ('public transport punctuality in one German region') plus the concrete metrics: share of trips more than 5 minutes late, cancelled stops, trend, and trip count. It also differentiates itself from line/station-level tools by explicitly stating that per-line realtime is not available.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives clear positive triggers: 'when the user asks whether buses and trains are running normally, or whether a strike or storm is disrupting local transport.' It also gives explicit negative guidance: do not use for one line, trip, or station, and notes that region-wide aggregates are the only answer. This effectively routes an agent away from inappropriate uses.

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

Deploy Server

Other Tools