Skip to main content
Glama

get_stop_info

Read-onlyIdempotent

Fetch detailed stop information—coordinates, codes, SIRI references, and serving lines—by stop ID to identify transit stations in Île-de-France.

Instructions

Get a Navitia station/stop's coordinates, codes, stops, SIRI references and serving lines.

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": {
      "stop_id": "<stop_id>"
    },
    "name": "get_stop_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
stop_idYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
sourceNoÎle-de-France Mobilités — PRIM
statusNook
timezoneNoEurope/Paris
warningsNo
source_urlNohttps://prim.iledefrance-mobilites.fr/
retrieved_atNo
data_licence_urlNohttps://cloud.fabmob.io/s/eYWWJBdM3fQiFNm
data_licence_noteNoPRIM product terms apply. The SIRI catalogue also references ODbL; see product metadata before redistribution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

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, open-world, non-destructive, so the safety profile is covered. The description adds that the response includes codes, child stops, SIRI references and serving lines — useful context beyond the annotations — but says nothing about failure behavior for an unknown stop_id or about ID namespacing.

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 no filler; the most important information (what is returned) leads the sentence.

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?

An output schema exists, so return values need not be spelled out, and annotations carry the safety profile. The main remaining gap for a one-parameter lookup tool is the stop_id format, which is critical to calling it correctly and is absent from both the description and the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, and the description does not explain the expected stop_id format (e.g., a Navitia 'stop_area:XXX:YYY' style identifier). 'Navitia station/stop' hints at the source but leaves the identifier syntax entirely undocumented in both schema and description.

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 description uses a specific verb ('Get') plus a specific resource ('Navitia station/stop') and enumerates the payload (coordinates, codes, stops, SIRI references, serving lines), which clearly separates it from siblings like plan_journey or get_next_departures. It stops short of explicitly naming a sibling it is not, so a 4 rather than 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 Guidelines2/5

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

There is no explicit when-to-use guidance, no statement of when to prefer search_places or get_next_departures instead, and no prerequisites (e.g., that a Navitia stop id must be known first). Usage is only inferable from the field list.

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