Skip to main content
Glama

plan_journey

Read-onlyIdempotent

Plan Île-de-France public transport journeys from origin to destination, with departure or arrival times, wheelchair access, transfer limits, and allowed or excluded lines.

Instructions

Plan journeys using place IDs, longitude;latitude or unambiguous names. ISO dates use Europe/Paris; use datetime_represents=arrival for an arrival deadline. allowed_ids/excluded_ids accept official line, network and mode IDs. Durations are seconds.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "plan_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
originYes
datetimeNo
wheelchairNo
allowed_idsNo
destinationYes
excluded_idsNo
max_transfersNo
datetime_representsNodeparture

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description still adds real behavioral context — timezone interpretation of datetimes, the departure/arrival semantic, ID types accepted by filters, and that durations are in seconds. It stops short of describing result shape or how limit interacts with results, but the output schema exists to carry that.

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?

Four short, front-loaded statements with no filler; input formats come first and the interpretation rules follow. The one dangling fragment, "Durations are seconds," is terse to the point of ambiguity about which durations it refers to.

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?

Coverage of the routing-critical parameters is good and an output schema handles return values, but a 9-parameter planning tool with no schema descriptions leaves limit, max_transfers and wheelchair semantics undefined. An agent knows how to phrase origin and destination but not how to control result count or transfer constraints.

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?

With 0% schema description coverage the description must carry the load, and it does explain origin/destination formats, datetime timezone handling, datetime_represents, and allowed_ids/excluded_ids ID types. However, limit (default 3), wheelchair, and max_transfers receive no explanation at all, leaving a third of the parameters undocumented anywhere.

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 opening clause gives a specific verb and resource ("Plan journeys") and enumerates accepted origin/destination formats (place IDs, longitude;latitude, unambiguous names). It is unambiguous about what the tool does, but it never names a sibling such as check_journey_status or get_next_departures, so the agent must infer the boundary from names alone.

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?

Guidance is present but parameter-oriented rather than routing-oriented: it tells you to set datetime_represents=arrival for an arrival deadline and that ISO dates are interpreted in Europe/Paris. There is no explicit statement of when to choose this over checking an existing journey or listing next departures.

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