Skip to main content
Glama

Service changes

service_notices
Read-onlyIdempotent

Lists current and announced service changes in a city network, such as closed stations, skipped stops or diversions, for every route or for one route by code, name or service. plan_journey, place_departures and route_details already include the changes on the routes they use.

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": {
      "city": "<city>"
    },
    "name": "service_notices"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity network from find_places or list_cities, such as Lahore, Attock or Rawalpindi.
routeNoRoute code, name or service. Leave out for every change in the city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that both current and announced (future) changes are returned, which is useful context, but says nothing about result volume, ordering or pagination.

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 sentences, zero filler: the first front-loads scope and content, the second handles the sibling overlap. Every clause carries information.

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?

For a two-parameter read-only tool with full schema coverage and clear annotations, the description covers purpose, scope and sibling overlap adequately. Only the return characteristics (if any uncertainty there) remain unaddressed, which is minor here.

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 100%, and the schema itself specifies the city source (find_places/list_cities) and that route accepts code, name or service with omission meaning all changes. The description restates the route flexibility but adds no format or matching details beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("lists current and announced service changes") plus concrete examples of what a change is (closed stations, skipped stops, diversions) and the scope (whole city network or a single route). The closing sentence differentiates it from route-detail siblings.

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?

Tells the agent it can be used city-wide or narrowed to one route, and warns that plan_journey, place_departures and route_details already surface changes on their routes — an implicit 'you may not need this call'. No explicit 'use this when' trigger is spelled out, so not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.