Skip to main content
Glama

get_next_departures

Read-onlyIdempotent

Retrieve upcoming real-time departures for an Île-de-France transit stop, optionally filtered by line or destination, with theoretical schedules clearly labeled when realtime is unavailable.

Instructions

Get next departures. A verified STIF SIRI MonitoringRef queries realtime. Navitia IDs use verified source codes to resolve SIRI refs. timetable=auto tries realtime then explicitly labels theoretical fallback; realtime never silently falls back. Direction filters match destination text.

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_next_departures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
line_idNo
stop_idYes
directionNo
timetableNoauto

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.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive. The description adds genuinely new behavioral context: realtime is explicitly labeled when theoretical fallback occurs and never silently substitutes, and direction filters match destination text. That is real value an agent could not get from the structured fields.

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?

Purpose is front-loaded in the first sentence, then each subsequent sentence adds a distinct behavioral fact about data resolution, fallback, or direction filtering. The jargon (SIRI, MonitoringRef, Navitia) is dense but earns its place for the domain.

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 explained, and annotations cover the safety profile. However, with five parameters at 0% schema coverage, gaps remain around limit semantics and line_id usage that an agent would need to guess.

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 description coverage is 0%, so the description must carry parameter meaning. It does explain stop_id formats (verified STIF SIRI MonitoringRef vs Navitia IDs resolved from verified source codes), timetable=auto, and direction destination-text matching, but says nothing about limit or line_id.

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?

Opens with a specific verb+resource: 'Get next departures.' The following sentences clarify data sources and fallback behavior, which reinforces scope. It doesn't name a sibling to contrast against, so an agent must infer the boundary with plan_journey or get_line_status.

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?

The description explains how timetable=auto behaves but never says when to choose this tool over alternatives like plan_journey or get_stop_info. There are no exclusions or prerequisites stated, leaving tool selection to inference.

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