Skip to main content
Glama

proximos_buses

Read-onlyIdempotent

Get upcoming bus departures from a Bogotá SITP or TransMilenio stop or station, with optional route, date, and time filters; falls back to scheduled data when realtime is unavailable.

Instructions

Próximos buses que salen de un paradero o estación.

Sin hora/fecha usa la hora actual de Bogotá e intenta usar el GTFS Realtime oficial; si no está disponible, usa el horario programado (se indica en "fuente"). hora en formato "HH:MM" (o "6:15 pm"), fecha en formato "AAAA-MM-DD". ruta filtra por código de ruta (ej. "B72").

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": {
      "paradero": "<paradero>"
    },
    "name": "proximos_buses"
  }
}

Input Schema

NameRequiredDescriptionDefault
horaNo
rutaNo
fechaNo
limiteNo
paraderoYes
ventana_minNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds meaningful behavior beyond them: the realtime-vs-scheduled fallback logic and the fact that the source is flagged in a 'fuente' field, which tells the agent how trustworthy the timing is. It does not disclose rate limits or how many results are typical relative to limite.

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?

Purpose is front-loaded in the first line, followed by conditional behavior and parameter formats; there is no filler. The line-broken phrasing is slightly fragmented but still easy to parse.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description only gestures at the response via the 'fuente' field, without describing what each returned bus entry contains. Combined with undocumented limite and ventana_min parameters, an agent can call it but cannot predict the result shape or the meaning of two defaults.

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 must carry the load: it documents hora and fecha formats (with an example like '6:15 pm') and explains that ruta filters by route code (e.g. 'B72'). But three parameters are left unexplained — the required paradero, limite (default 20), and ventana_min (default 60) — leaving real gaps despite the useful format detail.

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 ('Próximos buses que salen de un paradero o estación'), which is immediately distinguishable from siblings like rutas_en_paradero or buscar_paraderos. An agent knows exactly which result set this returns without opening the schema.

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?

Explains the conditional behavior when hora/fecha are omitted (current Bogotá time, GTFS Realtime first, scheduled fallback), which implicitly tells the agent when defaults apply. However, it never states when to prefer this over sibling tools or any exclusions/limitations on its use.

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