Skip to main content
Glama

get_line_status

Read-onlyIdempotent

Retrieve current and scheduled disruptions for an Île-de-France transit line by name or ID, with optional since/until date-times to filter alerts.

Instructions

Get line disruptions using a name (Métro 11, RER A, T3b) or line ID. Distinguishes current and scheduled alerts. since/until are optional ISO date-times.

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": {
      "line": "<line>"
    },
    "name": "get_line_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYes
sinceNo
untilNo

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

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

Annotations already declare this as a safe, idempotent, read-only, open-world operation, so the description needn't restate safety. It does add useful behavioral context that results separate current from scheduled alerts, but says nothing about pagination, result volume, or what happens for an unknown line.

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 with the core purpose front-loaded, followed by the behavioral detail about alert types and the optional date parameters. No filler or redundancy.

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?

With rich annotations, an output schema, and only three parameters, the description supplies enough input-format detail for correct invocation. Minor gaps remain around what the date window actually filters and any error behavior for unrecognized lines.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the full burden and mostly meets it: the 'line' parameter accepts a name in several formats or an ID, and since/until are flagged optional with an ISO date-time format. It still leaves the semantics of the since/until window (alert start vs. validity period) implicit.

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 states a specific verb and resource ('Get line disruptions') and grounds it with concrete line-name examples (Métro 11, RER A, T3b) as well as line IDs, so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from the sibling get_network_disruptions, which keeps it below 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 Guidelines3/5

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

Usage is only implied: the reader infers this is the tool for a single line's disruptions, and 'Distinguishes current and scheduled alerts' hints at why the since/until window matters. No explicit when-to-use vs when-not guidance and no named alternative for network-wide queries is given.

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