Skip to main content
Glama

search_stations

Read-onlyIdempotent

Search public transport stations and stops by name or coordinates to locate Swiss stops for journey planning and geodata lookup.

Instructions

Search public transport stations/stops by name or coordinates

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoLatitude (WGS84)
yNoLongitude (WGS84)
typeNo
queryNoStation name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.9.0
    • changedInput schema / properties / query / description
      Previous value: -"Station name to search for"New value: +"Station name"
    • removedInput schema / properties / type / description
      Removed value: -"Filter: all, station, poi, address"
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "all",
      +  "station",
      +  "poi",
      +  "address"
      +]
    • 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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only the domain restriction to public transport, but says nothing about result limits, ranking, match tolerance, or whether query and coordinates can be combined.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, but the terseness comes at the cost of coverage rather than from disciplined editing.

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?

Zero required parameters and no output schema mean the agent has no idea what a call with no arguments returns, what fields a station carries, or whether the returned identifier is the input other station tools (get_departures, get_station_accessibility) expect. For a discovery tool that likely feeds those siblings, that context is essential.

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 75% and both x/y and query are documented there, so the baseline is 3. The description does clarify that name and coordinates are alternative search modes, but it never explains the undocumented `type` enum (all/station/poi/address) or what happens when all four optional params are omitted.

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 (search) and a specific resource (public transport stations/stops), plus the two lookup modes (name or coordinates). That scope alone separates it from generic geocoding siblings like geocode or search_places, though it never names an alternative explicitly.

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?

No when-to-use or when-not-to-use guidance. With siblings such as get_nearby_stations, list_ogd_stations and geocode in the same namespace, an agent gets no signal about which call to prefer for proximity vs. name 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