Skip to main content
Glama

Find stations near coordinates

get_nearby_stations
Read-only

Find public transport stations near a WGS84 latitude/longitude point, sorted by distance. Specify coordinates and an optional result limit to locate nearby stops.

Instructions

Find public transport stations near a WGS84 point, sorted by distance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_nearby_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude
lonYesWGS84 longitude
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds one genuinely useful behavioral fact — results are sorted by distance — but says nothing about how the search radius is bounded, how many results come back by default, or what happens when nothing is near the point.

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?

A single front-loaded sentence with no filler; the coordinate system and the distance sorting, the two facts an agent most needs, both land immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should carry more of the return-value burden than it does — it discloses sorting but not the result shape or the number of records. For a low-complexity two-required-parameter lookup it is adequate, but the absence of any effective-radius or pagination note leaves a real behavioral gap.

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 67%: lat and lon are self-documented as WGS84, and the description's "WGS84 point" phrasing only reinforces the coordinate reference system. The limit parameter (default 15, max 50) carries no descriptive meaning in either the schema or the description, which is the one real gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Find public transport stations") plus the spatial qualifier ("near a WGS84 point"), which cleanly separates it from nearby-style siblings covering dams, EV chargers or vehicles. It stops short of naming any alternative explicitly, so sibling differentiation is implied by the resource noun rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what the tool does but never when to choose it over search_stations or the other *_nearby tools, and gives no preconditions, radius assumptions, or exclusions. An agent must infer from the resource noun alone that this is the coordinate-based station lookup.

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