Skip to main content
Glama

Swiss public transport

stations_nearby

Read-only

The stops closest to a point, with their distance in metres.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "stations_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesWGS84 latitude, e.g. 46.9488.
longitudeYesWGS84 longitude, e.g. 7.4391.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description usefully states that distances are in metres, but it never says how many stops 'closest' returns or whether there is a radius cap, which matters for a proximity query.

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 key scope (closest stops, metric distance) appears first. Nothing in it is redundant.

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?

With an output schema present, the description need not explain return values, and the two required coordinates are fully documented. The remaining gap is result-set behaviour (count, radius, tie handling) for a proximity tool, which the description leaves unstated.

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 both coordinate parameters carry format examples, so the schema does the heavy lifting. The description adds only that the point is a spatial anchor for proximity, not any new meaning for latitude/longitude.

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?

"The stops closest to a point, with their distance in metres" names the resource (stops) and the spatial relation (proximity to a point), which is more specific than the name alone. It does not, however, distinguish this from the sibling find_stations, so an agent cannot tell from the text alone which proximity tool to pick.

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 or when-not-to-use guidance and no mention of alternatives such as find_stations. Usage is only implied by the phrase 'closest to a point'; the agent must infer the scenario and the boundary against siblings.

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