oasa-mcp

List transit lines

list_lines

Read-only

Search or list OASA Athens transit lines by rider-facing number or Greek/Latin name to find bus, trolley, metro, and tram routes. Narrow results with a query and confirm totals.

Instructions

List or search OASA lines. Match by the rider-facing number ("040", "Α1", "X95", matched exactly) or by name in Greek or Latin characters. There are around 470 lines, so always pass a query unless you genuinely need a sample; the total is reported so you can tell whether to narrow. Covers Attica (greater Athens) only: OASA buses, trolleys, metro and tram.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No	Line number or name fragment.
`language`	No	Which name language to show. 'both' pairs the Greek name with the English.	both

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld), but the description adds real operational context: exact-match semantics for the number, ~470 total lines, the reported total, and a hard geographic boundary (Attica only, OASA buses/trolleys/metro/tram). It omits pagination/ordering behavior, which is the main remaining unknown.

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?

Three front-loaded sentences: purpose, matching rules, then scoping/caution. Each sentence carries distinct information (verb, match keys, size warning, coverage boundary) with no filler.

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?

With no output schema, the description usefully notes the total is reported, and it bounds scope to Attica. Minor gaps remain around result ordering/pagination, but for a 3-param read-only discovery tool this is essentially complete.

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 67%, so the schema documents query and language but leaves limit bare. The description adds genuine meaning by specifying that matching is exact on the number and supports Greek or Latin names, which is not derivable from the schema alone.

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 ("List or search OASA lines") plus the two match keys (rider-facing number vs. name). This clearly separates it from siblings like find_stops, line_routes and line_schedule, which operate on stops or a single line's structure.

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?

Gives explicit operating guidance: "always pass a query unless you genuinely need a sample", and explains the total-count signal for deciding to narrow. It does not, however, route the agent to a sibling (e.g. line_routes for a line's path once the code is known), so it stops short of full when/when-not/alternatives guidance.

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

Deploy Server