Skip to main content
Glama

get_network_disruptions

Read-onlyIdempotent

Retrieve paginated public transport network alerts, optionally filtered by line, physical mode, and ISO time range, and page results with offset to monitor disruptions.

Instructions

Get paginated network alerts, optionally scoped by exact line or physical mode ID and ISO since/until. Check complete before interpreting absent alerts; use next_offset to page concise output (default 20 alerts).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_network_disruptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
untilNo
offsetNo
line_idNo
physical_mode_idNo

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
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the bar is lower. The description nonetheless adds non-obvious behavioral facts: results are paginated with a default page of 20, output is 'concise', and absent alerts are only meaningful once the result set is confirmed complete — a genuine correctness caveat not present in the annotations.

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?

Two tight sentences, front-loaded with the resource and scope before the operational caveats. Dense but every clause carries information; only the 'next_offset' naming could be tightened to match the schema.

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 and annotations are rich, so return shape and safety need not be restated. Against six optional parameters the description covers scoping, time filtering, page size and the completeness caveat adequately, with the offset/paging naming as the main residual ambiguity.

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%, so the description must carry all six parameters. It does explain exact-match semantics for line_id/physical_mode_id, ISO format for since/until, and the default of 20 for limit, but leaves offset's meaning implicit and refers to it as 'next_offset', wording that does not match the schema property name and risks confusing the agent about what to pass.

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 paginated network alerts') and states the two optional scoping dimensions (exact line or physical mode ID, ISO since/until). This is clearly distinct from siblings like get_line_status or get_next_departures, though the description never explicitly contrasts with them.

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?

Gives real usage guidance for interpretation ('Check complete before interpreting absent alerts') and for paging ('use next_offset to page concise output'), which is more than most. It does not, however, say when to prefer this tool over line-specific siblings such as get_line_status, so the when-to-use condition remains implied.

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