Skip to main content
Glama
vbhjckfd

mcp-lad-lviv-ua

by vbhjckfd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Get Stop Realtime

get_stop_realtime
Read-onlyIdempotent

Returns live arrivals and vehicle positions for a given stop. Enter a numeric stop ID to get real-time timetable data and a map view.

Instructions

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.11
  2. Removedv1.0.9
  3. Changed2 schema fields changedv1.0.8
    • changedInput schema / properties / stop_id / anyOf
      Previous value: -[
-  {
-    "description": "Numeric municipal stop code (e.g. 707).",
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  },
-  {
-    "description": "Municipal stop code as digits-only string (e.g. \"707\").",
-    "pattern": "^\\d+$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "description": "Positive integer stop code (e.g. 707).",
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "description": "Stop code as a digits-only string (e.g. \"707\").",
+    "pattern": "^\\d+$",
+    "type": "string"
+  }
+]
    • addedInput schema / properties / stop_id / description
      Added value: +"Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string."
  4. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent. The description adds that it produces a map UI block and structured list, which is behavioral context beyond 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?

Two sentences with essential information, front-loaded with purpose, and no extraneous words. Every sentence earns its place.

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 tool with one parameter, full schema coverage, and output schema, the description covers all necessary aspects: functionality, usage context, parameter source, and sibling relationships.

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 100%, so baseline 3. The description adds value by explaining how to obtain the stop ID (from signage) and when to use a different tool for other inputs, exceeding mere schema details.

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, specifying both a map UI block and structured arrival list. It distinguishes itself from siblings like `get_stop_geometry` and `get_stops_around_location`.

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 says to use as default for arrivals/departures, prefers `get_stop_geometry` for static data, and suggests `get_stops_around_location` for address/coordinate inputs. Provides clear when-to-use and alternatives.

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