Skip to main content
Glama
vbhjckfd

mcp-lad-lviv-ua

by vbhjckfd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Get Stops Around Location

get_stops_around_location
Read-onlyIdempotent

Find nearby transit stops by providing latitude and longitude. Returns numerical stop codes, names, coordinates, and walking distance to enable further timetable queries.

Instructions

Discovers transit stops near a geographic point, returning each stop's numeric code, name, coordinates, and walking distance. Also emits a map UI block with multiple markers for map-capable clients (e.g. ChatGPT). Use this as the first step whenever the user provides an address, place name, or coordinates and you need stop IDs before calling get_stop_realtime or get_stop_geometry. Do NOT use this to fetch arrivals or live vehicle data — it returns stop metadata only. Default radius is 1 000 m; narrow it (e.g. 300 m) for dense urban areas or widen it (up to 3 000 m) for rural locations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesDecimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv).
longitudeYesDecimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv).
radius_metersNoSearch radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas.

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. Changed3 schema fields changedv1.0.8
    • changedInput schema / properties / latitude / description
      Previous value: -"Center latitude (WGS84)."New value: +"Decimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv)."
    • changedInput schema / properties / longitude / description
      Previous value: -"Center longitude (WGS84)."New value: +"Decimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv)."
    • changedInput schema / properties / radius_meters / description
      Previous value: -"Search radius in meters (default 1000; same cap as the public /closest API)."New value: +"Search radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas."
  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 declare readOnlyHint=true and idempotentHint=true, so safety profile is clear. Description adds valuable context: emits a map UI block for map-capable clients, default radius is 1000 m, and valid radius range (50–3000). This goes beyond annotations without contradicting them.

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?

Description is efficiently structured: first sentence states primary function and added map UI block, second sentence provides usage guidance and exclusions, third sentence offers radius optimization tips. No redundant or superfluous information; 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?

Given that an output schema exists (so return structure need not be described), the description is complete: it covers purpose, when to use, when not to use, and parameter behavior. Context signals (3 params, 2 required, 100% schema coverage, sibling tools) are fully addressed by the description.

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?

Input schema already covers all parameters with descriptions (100% coverage). Description adds no new parameter details but provides usage context: default radius (1000 m), suggested values for dense urban (300 m) vs rural (3000 m), and clarifies that latitude/longitude use WGS84. This added value justifies a score above baseline 3.

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?

Description clearly states the tool discovers transit stops near a geographic point, returning specific metadata (code, name, coordinates, distance) and a map UI block. It distinguishes itself from sibling tools like get_stop_realtime (arrivals) and get_stop_geometry (geometry), ensuring unambiguous purpose.

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 the first step when needing stop IDs before calling get_stop_realtime or get_stop_geometry, and warns not to use for arrivals or live data. Also provides radius adjustment guidance for dense urban vs rural areas, leaving no ambiguity about when to employ this tool.

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