Skip to main content
Glama

Swiss public transport

find_stations

Read-only

Find stations and stops by name. Returns their exact names and ids, best match first.

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": "find_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesName or part of a name, e.g. 'Bern' or 'Basel, Bank'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and open-world, so safety is covered. The description adds genuinely new behavioral context beyond them: results are ranked with the best match first and include exact names plus ids, which tells the agent how to interpret ordering and use the output for chaining.

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?

Two short sentences, no filler, with the primary purpose front-loaded and the return ordering stated second. Every sentence earns its place.

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

Completeness4/5

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

For a one-parameter lookup with a full output schema and complete annotations, the description covers purpose, matching key and result ordering, which is nearly everything an agent needs. Minor gaps remain around fuzzy-match behavior or what happens when no station matches.

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 100% and the single query parameter already carries an example ('Bern', 'Basel, Bank'). The description's phrase 'by name' restates the schema rather than adding syntax, length limits, or matching rules, so the baseline 3 applies.

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 and resource: 'Find stations and stops by name' tells the agent exactly what is searched and by which key. It implicitly separates itself from siblings like stations_nearby or departures, though it never names an alternative explicitly, which keeps it just short of a 5.

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 the phrase 'by name' — an agent can infer this is the lookup path when it has a partial name and needs an id. There is no explicit statement of when not to use it or which sibling to prefer for proximity or schedule queries, so guidance stays at the minimum viable level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources