Skip to main content
Glama

buses_ruta

Read-only

Fetch all variants for a TransMilenio route code, including origin, destination, direction, stops, duration, and live bus locations; add coordinates to get the nearest stop and upcoming arrivals.

Instructions

Variantes de una ruta y dónde van ahora sus buses.

ruta: el código del bus o la estación ("B10", "C25", "H710", "16-8"). Un código puede tener varias variantes (C25 troncal y C25 zonal, ida y regreso): cada una trae origen, destino, sentido ("Sur-Norte", "Circular"), número de paradas, duración típica y sus buses. Con lat/lon del usuario, cada variante trae tu_parada: su paradero más cercano y en cuántos minutos pasan los próximos buses por ahí.

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": {
      "ruta": "<ruta>"
    },
    "name": "buses_ruta"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
rutaYes
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description goes beyond that by describing what each variant returns (origen, destino, sentido, número de paradas, duración típica, buses) and that lat/lon adds a `tu_parada` with minutes-to-arrival — valuable since there is no output schema. It does not mention rate limits, real-time staleness, or what happens when a code matches no route.

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?

Two short paragraphs, front-loaded with the purpose followed by parameter semantics. The examples are compact and earn their place by showing code formats. No filler or repeated 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?

With no output schema, describing the returned variant fields is exactly what an agent needs, and the description does that plus the optional-geolocation behavior. The only gap is the undocumented `limite` parameter and the lack of guidance on handling empty results for an unknown route code.

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 burden. It does well for `ruta` (accepts bus or station codes like "B10", "C25", "H710", "16-8" and explains that one code can yield multiple variants) and for `lat`/`lon` (they enable `tu_parada`), but `limite` (default 40) is never mentioned, leaving one parameter unexplained.

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 line states a concrete purpose: the variants of a route and where its buses currently are. The detail about origen/destino/sentido/paradas/duración makes the scope unambiguous. It lacks explicit naming of siblings (e.g. llegadas, proximas_paradas) that an agent might confuse it with, 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 Guidelines3/5

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

Usage is only implied: the description makes clear you need a route or station code and that adding lat/lon unlocks the nearest-stop info. There is no explicit when-to-use / when-not-to-use statement and no routing to alternatives such as a tool that gives plain arrivals for a single stop.

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