Skip to main content
Glama

check_journey_status

Read-onlyIdempotent

Check a planned journey against line alerts to flag potentially affected segments and assess disruptions; unavailable information does not mean all clear.

Instructions

Check one journey returned by plan_journey against line alerts. Flags potentially affected segments; unavailable information never means all clear.

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": {
      "journey": "<journey>"
    },
    "name": "check_journey_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
journeyYes

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.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine semantic value with 'Flags potentially affected segments' and the caveat that missing data is not an all-clear, but it says nothing about severity, confidence, or the cost/latency of the check.

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 tight sentences, front-loaded with the action and immediately followed by the most important interpretive caveat. Nothing is repeated from the name or annotations and there is no filler.

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?

An output schema exists so return values need no explanation, and the description covers the input's provenance plus the unknown-data caveat. Given a free-form nested object parameter, one more sentence on the journey's expected structure would have made it complete.

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 0% and the single journey parameter is an untyped nested object with additionalProperties, so the schema explains almost nothing. The description partially compensates by telling the agent the object comes from plan_journey's output, but it never describes the expected shape or which fields are read.

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?

Specific verb+resource: 'Check one journey ... against line alerts', with the scope limited to a single journey and a nod to its originating sibling plan_journey. It does not explicitly contrast itself with get_line_status or get_network_disruptions, so the differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Establishes a clear precondition and ordering: the journey must be one 'returned by plan_journey', which tells the agent to plan first, then check. It stops short of naming when-not-to-use or an alternative for line-wide status questions.

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