Skip to main content
Glama

get_nearby_stations

Read-onlyIdempotent

Find Swiss public transport stations near WGS84 coordinates, with optional result limit and maximum distance filters.

Instructions

Stations near coordinates

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "get_nearby_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesLatitude (WGS84)
yYesLongitude (WGS84)
limitNoMax results
distanceNoMax distance (m)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • changedInput schema / properties / distance / description
      Previous value: -"Max distance in meters"New value: +"Max distance (m)"
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results (default: 10)"New value: +"Max results"
    • changedInput schema / properties / x / description
      Previous value: -"Longitude (WGS84)"New value: +"Latitude (WGS84)"
    • changedInput schema / properties / y / description
      Previous value: -"Latitude (WGS84)"New value: +"Longitude (WGS84)"
  2. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered by structured data. The description adds nothing beyond that: it does not say what happens when the radius is omitted, whether results are sorted by distance, whether there is a default or maximum distance, or what station domain is being queried.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four words with zero waste, but the brevity is under-specification rather than efficiency — there is no verb, no scope, and no front-loaded context an agent can act on. Short is good here only in the sense that nothing needs trimming.

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

Completeness2/5

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

For a 4-parameter geospatial query in a large API surface full of station-related tools, with no output schema, the definition leaves the agent guessing at station domain, result ordering, default radius, and return shape. Annotations and the schema cover safety and parameter meaning, but the core "what do I get back and which stations" question is unanswered.

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 description coverage is 100% with per-parameter descriptions for x (latitude WGS84), y (longitude WGS84), limit, and distance (metres), so the schema carries the semantics. The description adds no meaning beyond that, which is the baseline-3 case.

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

Purpose2/5

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

"Stations near coordinates" is essentially a restatement of the tool name (get_nearby_stations) rather than a distinct statement of purpose. It does convey a geospatial-proximity resource, but it never says which kind of stations (transit, weather, hydro, OGD) or what unit/scope applies, leaving it indistinguishable from siblings like search_stations, list_ogd_stations, and buildings_near.

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?

There is no when-to-use guidance, no when-not-to-use, and no named alternative. An agent trying to choose between this and search_stations, list_snow_stations, list_hydro_stations, or get_trail_closures_nearby gets no routing signal at all beyond the word "nearby".

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