Skip to main content
Glama
fabianhogger

oasa-mcp

by fabianhogger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Live arrivals at a stop

stop_arrivals
Read-only

Fetches live next-vehicle arrival times in minutes for a chosen OASA stop, including line and destination. Enter a stop name (Greek/Latin) or exact stop code.

Instructions

Live next-vehicle arrivals for one OASA stop, in minutes, with each vehicle joined to its line number and destination. Accepts a stop name in Greek or Latin characters ("Syntagma", "ΣΥΝΤΑΓΜΑ") or an exact stop_code. If a name matches several stops the candidates are returned instead of one being guessed. An empty result is normal and not an error — outside roughly 05:00-00:30 Europe/Athens most lines are not running. Minutes are OASA's own live estimates, not timetable times; use line_schedule for scheduled departures. Covers Attica (greater Athens) only: OASA buses, trolleys, metro and tram.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineNoDisambiguate the stop by a line that serves it, and filter to that line.
stopYesStop name (Greek or Latin characters) or an exact numeric stop_code.
limitNo
languageNoWhich name language to show. 'both' pairs the Greek name with the English.both

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds real operational context: minutes are live OASA estimates rather than timetable times, an empty result is normal rather than an error with the reason given, multi-match names return candidates instead of a guess, and coverage is Attica-only. This is disclosure well beyond the annotations.

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 core purpose and scope lead, followed by input handling, empty-result semantics, and the sibling alternative. Five dense sentences with no filler; every clause carries information an agent could act on.

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 still describes the return content (per-vehicle line number and destination, in minutes) and the empty/ambiguous cases. Geographic and time-window limits round out what an agent needs to call and interpret this correctly.

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 coverage is 75%, and the description reinforces the stop parameter's dual form (Greek/Latin name or exact stop_code) and the ambiguity/candidate behavior, which the schema does not state. It adds nothing for limit or language, but those are partly documented in the schema, so the marginal gain is real if partial.

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 and resource ('Live next-vehicle arrivals for one OASA stop, in minutes') plus the shape of each returned item (vehicle joined to line number and destination). It also scopes coverage to Attica and OASA modes, which no sibling covers.

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?

Explicitly routes to the alternative ('use line_schedule for scheduled departures') and explains when an empty result is expected (outside roughly 05:00-00:30 Europe/Athens). It also tells the agent how to disambiguate via stop name vs. exact stop_code, which is exactly the when-to-use decision an agent needs.

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