Skip to main content
Glama
carris-metropolitana-mcp

carris-metropolitana-mcp

next_arrivals

Get upcoming bus arrivals for a Carris Metropolitana stop, showing real-time or scheduled times and minutes until each bus departs. Use it to answer when the next bus at a stop is due.

Instructions

Upcoming buses at a Carris Metropolitana stop, real-time where available.

Use for "when is the next bus at X?" (get stop_id from find_stops first). Each arrival says whether it is "realtime" (live GPS estimate) or "scheduled" (timetable only: the bus may not have started its trip yet). minutes_from_now uses the real-time estimate when present. Times are Europe/Lisbon. Only today's operational day is covered, so late at night the list may be short or empty.

Args: stop_id: 6-digit stop id, e.g. "060361". line_id: Optional 4-digit line number to keep only that line, e.g. "2794". limit: Max arrivals to return (default 10, max 50).

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": {
      "stop_id": "<stop_id>"
    },
    "name": "next_arrivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
line_idNo
stop_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/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 so: it explains the realtime vs scheduled distinction, that minutes_from_now prefers the live estimate, the Europe/Lisbon timezone, and the operational-day limitation. These are non-obvious behavioral traits an agent could not infer from the schema.

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?

Front-loaded with purpose and trigger, then behavioral caveats, then per-parameter notes — good ordering with no filler. The args block slightly restates type information that the schema already encodes, but it is earning its place given the 0% schema coverage.

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?

Output schema exists, so return structure need not be explained, yet the description still clarifies how to read each arrival (realtime flag, scheduled caveat, minutes_from_now). For a 3-parameter read tool with no annotations, nothing an agent needs to call it correctly is missing.

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%, so the description must compensate and it does: stop_id format (6-digit, example "060361"), line_id (optional 4-digit line, example "2794"), and limit with both default and max (default 10, max 50). That is meaningfully more than the bare schema types.

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+resource+scope: upcoming bus arrivals at a Carris Metropolitana stop, real-time where available. It also names the sibling find_stops as the source of the required stop_id, so the agent can orient without opening schemas.

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?

Gives an explicit trigger phrase ("when is the next bus at X?") plus the prerequisite step (get stop_id from find_stops first). It also flags a boundary condition — late at night the list may be short or empty — which tells the agent when results should be interpreted cautiously.

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