transmilenio

llegadas

Read-only

Retrieves upcoming bus arrivals for a TransMilenio station or stop, including route, destination, estimated minutes, and delay so users can plan trips.

Instructions

Próximos buses que llegan a una estación o paradero, del más cercano al más lejano.

parada: nombre ("Calle 72") o id de buscar_parada. En una estación incluye sus vagones. minutos: ventana de búsqueda, máximo 90. ruta: deja solo esa ruta ("¿cuándo pasa el B10 por Calle 72?"). Cada llegada trae ruta, destino, sentido, minutos y hora estimados, paradas que le faltan, vagón, número del bus, placa y retraso en segundos (positivo = tarde).

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": {
      "parada": "<parada>"
    },
    "name": "llegadas"
  }
}

Input Schema

Name	Required	Description	Default
`ruta`	No
`limite`	No
`parada`	Yes
`minutos`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare read-only and open-world; beyond that, the description discloses the 90-minute maximum search window, the default sort order, station vs. stop behavior (platforms included), and the sign convention for delay (positive = late). It says nothing about failure modes such as an unrecognized stop name or rate limits, so it is strong but not exhaustive.

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 core behavior and ordering are front-loaded in the first sentence, then parameters are paragraph-labeled, and every sentence carries information. Some line-break fragmentation and the parenthetical example are minor overhead rather than waste.

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 no output schema, the description usefully enumerates the return fields (route, destination, direction, minutes, ETA, remaining stops, platform, bus number, plate, delay). The only substantive omission is `limite`, plus any note on what happens when no arrivals match.

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 0%, so the description carries the full burden and it explains three of four parameters well (`parada` accepted formats, `minutos` max 90, `ruta` as a filter). The `limite` parameter (default 20) is never mentioned, leaving a real gap.

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 opening sentence names a specific verb+resource (upcoming bus arrivals at a station/stop) and adds ordering semantics (nearest to farthest). It does not explicitly contrast itself with arguably overlapping siblings like proximas_paradas or buses_cerca, so it stops short of 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 Guidelines4/5

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

It gives an explicit usage pattern via the quoted example ("¿cuándo pasa el B10 por Calle 72?") and tells the agent that `parada` can come from a prior `buscar_parada` call, which establishes a prerequisite flow. It lacks explicit when-not-to-use guidance or named alternatives.

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

Deploy Server