Skip to main content
Glama
carris-metropolitana-mcp

carris-metropolitana-mcp

service_alerts

Check current bus disruptions, detours, strikes, and unserved stops for Carris Metropolitana, filtering by line or stop before recommending a trip.

Instructions

Service alerts (detours, works, strikes, stops not served) for Carris Metropolitana.

Use before recommending a trip, or when the user asks "is line X disrupted?". Filter by line and/or stop; with no filter, returns all current alerts (there are often ~100). Alerts are mostly published in Portuguese only.

Args: line_id: 4-digit line number, e.g. "4407". stop_id: 6-digit stop id, e.g. "160584". include_upcoming: Also return alerts that start in the future (default True). language: Preferred language ("pt" or "en"); falls back to what exists. limit: Max alerts to return (default 20, max 100).

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": "service_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
line_idNo
stop_idNo
languageNopt
include_upcomingNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it warns that an unfiltered call returns ~100 alerts, that alerts are mostly Portuguese-only with a language fallback, and that include_upcoming defaults to True. It omits auth/rate-limit context and does not explicitly state the operation is read-only, which keeps it just short of a 5.

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?

The summary line is front-loaded, followed by usage and a scannable Args block, so an agent can extract what it needs quickly. There is minor redundancy in restating schema defaults (limit 20, include_upcoming True), but the added format examples justify most of the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 not be described, and the description covers everything else an agent needs: purpose, trigger conditions, all five parameters with examples, the unfiltered-call volume risk, and the Portuguese-only caveat. Nothing material is missing for correct invocation.

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

Parameters5/5

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

Schema description coverage is 0%, yet the Args block documents all five parameters with formats and defaults: 4-digit line_id with example "4407", 6-digit stop_id with example "160584", include_upcoming default True, language values pt/en with fallback behavior, and limit default 20 / max 100. This fully compensates for the empty schema descriptions.

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?

The first sentence names a specific resource (service alerts) and enumerates its content types (detours, works, strikes, stops not served) for a named operator. That is clearly distinguishable from siblings such as next_arrivals, line_info, and vehicle_positions, which cover schedules, line metadata, and vehicles rather than disruptions.

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

Usage Guidelines5/5

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

It states explicit triggers — "Use before recommending a trip, or when the user asks 'is line X disrupted?'" — and explains the filtering decision (filter by line and/or stop) plus the consequence of not filtering. That covers both when to use it and how to scope the call, leaving little to inference.

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