Skip to main content
Glama

ranking_rutas

Read-only

Order TransMilenio routes by bus counts, schedule compliance, delays, or scheduled trips to compare service, optionally filtered by date, time window, and system.

Instructions

Rutas ordenadas para comparar: cuál tiene más o menos buses, cuál cumple menos su horario.

criterio: "buses" (promedio en vía frente a lo programado), "cumplimiento" (viajes vistos sobre programados), "retraso" (minutos promedio frente al horario) o "programados" (viajes del horario, sin historial). orden: "mas" o "menos". desde_hora/hasta_hora: franja, p. ej. 6 y 9 para la hora pico de la mañana. sistema: "troncal", "zonal", "alimentador", "dual" o "transmicable".

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

Input Schema

NameRequiredDescriptionDefault
fechaNo
ordenNomas
limiteNo
sistemaNo
criterioNobuses
desde_horaNo
hasta_horaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful domain semantics, notably that 'programados' draws from schedule data with no history and that 'buses' compares average on-road against scheduled. It does not disclose return shape, defaults such as fecha being today, or limits, so it adds context without being rich.

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 purpose is front-loaded in one sentence, then parameters are explained in a compact structured pass using backticked field names. Dense but every clause adds information; no filler sentences.

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?

For a 7-parameter, no-output-schema tool, the definition covers the semantic questions well but leaves fecha and limite unexplained and gives no hint about the fields returned per route (e.g. route id, name, metric value), which an agent would want before presenting results. Adequate but with visible gaps.

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

Parameters4/5

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

Schema description coverage is 0% and there are no enums, so the description carries the burden and largely does: it enumerates all four criterio values, both orden values, all five sistema values, and explains desde_hora/hasta_hora with a worked example (6 and 9 for morning peak). Only fecha and limite are left undefined, which keeps it from a 5.

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 description opens with a specific verb+resource framing ('Rutas ordenadas para comparar') and gives two concrete comparison questions ('cuál tiene más o menos buses, cuál cumple menos su horario'). That distinguishes it from data-lookup siblings like historial_ruta or programacion_ruta, though it never names an alternative explicitly.

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?

The comparative/ranking intent is clear and the criterio list makes the use-case context obvious (comparing routes by fleet, schedule compliance, delay, or scheduled trips). There are no explicit when-not conditions or named alternatives, so it stops short of full routing guidance.

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