Skip to main content
Glama

Lviv Public Transport

by io.github.vbhjckfd

Get Stop Realtime

get_stop_realtime
Read-onlyIdempotent

Returns live arrivals and vehicle positions for a stop, producing both a map UI block and a structured arrival list. Use this as the default tool when the user asks about arrivals, departures, or vehicles at a specific stop. Prefer get_stop_geometry when only static route polylines are needed and live data is irrelevant. Requires a numeric stop ID (shown on stop signage); use get_stops_around_location first if you only have an address or coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stop_idYesMunicipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
viewYes
ui_blocksYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds useful context by stating it produces a map UI block and a structured list, and emphasizes 'live' data—details not available from annotations. No contradictions.

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 sentences, each earning its place: purpose, usage guidance, and parameter requirement. Front-loaded with the core action, no fluff.

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 one-parameter tool with an output schema and strong annotations, the description fully covers purpose, alternatives, prerequisites, and output nature. Nothing critical is missing.

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 coverage is 100%, with stop_id thoroughly described (municipal code, example 707, digit-only string accepted). The description merely repeats 'numeric stop ID (shown on stop signage)' adding no new information beyond the schema, so baseline 3 is appropriate.

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 clearly states the tool returns live arrivals and vehicle positions for a stop, and specifies the two output forms (map UI block and structured arrival list). It also distinguishes itself from sibling tools by explicitly naming get_stop_geometry as the static alternative.

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 explicitly names this as the default tool for arrival/departure/vehicle queries at a specific stop, provides an alternative (get_stop_geometry) for static data, and instructs using get_stops_around_location when only an address or coordinates are available. This is strong when/when-not guidance.

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

All Lviv Public Transport toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct resource (route, stop, vehicle, nearby) and mode (static vs. realtime), with clear cross-references that prevent overlap. The descriptions explicitly state when to prefer one tool over another, eliminating ambiguity.

Naming Consistency5/5

All tool names follow a strict get_<resource>_<modifier> pattern (e.g., get_route_realtime, get_stop_geometry), making the API predictable. Verb and noun usage is uniform throughout the set.

Tool Count5/5

Seven tools is a well-scoped size for a transit data server, covering static and realtime data for routes, stops, and vehicles. Each tool serves a necessary purpose with no redundancy.

Completeness4/5

Core workflows (discover stops by location, get route and stop data, track vehicles) are well covered. The only notable gap is lack of stop search by name; get_stops_around_location requires coordinates, so a stop name alone cannot resolve without external geocoding.

Resources