Skip to main content
Glama

Search public transport stations

search_stations
Read-only

Find Swiss public transport stations and stops by name or name fragment to match locations for route planning and transport queries.

Instructions

Search Swiss public transport stations and stops by name.

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": {
      "query": "<query>"
    },
    "name": "search_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesStation name or fragment, e.g. 'Interlaken'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/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 openness profile is covered. The description adds the geographic scope (Swiss) and lookup mode (name), which is genuine context, but says nothing about result ordering, truncation at the limit, or whether stops and stations are mixed in one list.

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 zero filler; the resource and the matching mode come first. Nothing is redundant with the title or restates the tool name without adding scope.

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?

For a two-parameter read-only search tool with annotations and a fully typed schema, the core is present. Still missing is what a result entry looks like (station ID, coordinates, canton) and how limit affects the response, which matters because there is no output schema to fall back on.

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 50%: the query parameter is already documented with an example, and the description only reinforces that it is a name fragment. The limit parameter (default 15, max 50) carries no explanation of whether it truncates, ranks, or paginates results, so the description does not compensate for the coverage 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 (search), a specific resource (Swiss public transport stations and stops), and a lookup mode (by name). This distinguishes it from get_nearby_stations or the weather/hydro/snow station listers, though the description itself never names those alternatives.

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

Usage Guidelines3/5

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

Usage is only implied: 'by name' tells the agent this is a name-fragment lookup, which rules out proximity or ID lookups by inference. There is no explicit statement of when to prefer this over get_nearby_stations, nor any note about empty results or query length constraints.

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