Skip to main content
Glama
Sign In
transmilenio

transmilenio

by PRestrepo2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

programacion_ruta

Read-only

Retrieve a route's official schedule for a given day, showing hourly trips and buses on the road. Use it to check trip counts or peak bus hours for a route.

Instructions

Lo que el horario oficial programa para una ruta un día: viajes por hora y buses en vía.

fecha: "hoy" (por defecto), "ayer" o "2026-11-06". Distingue hábil, sábado y festivo. No necesita historial. Sirve para "¿cuántos viajes tiene el C25 hoy?" o "¿a qué hora hay más buses del B10?".

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

Input Schema

NameRequiredDescriptionDefault
rutaYes
fechaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real behavioral context on top: the schedule differentiates weekday, Saturday and holiday, and the 'hoy' default is stated. It does not discuss response shape or any freshness/latency caveats, which keeps it below the top mark.

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 definition is front-loaded in one sentence, followed by a focused parameter note and two illustrative queries. The content is tight, though the line breaks and mixed prose make it slightly less scannable than a fully structured definition.

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?

For a two-parameter, read-only tool with no output schema and annotation coverage of its safety profile, the description supplies enough to call it correctly: the default date, accepted date forms, and the day-type distinction. The only real gap is the exact format expected for the route identifier, which is shown only by example.

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. It handles `fecha` well (accepted values "hoy"/"ayer"/ISO date, default, and that weekday/Saturday/holiday are distinguished) but leaves the required `ruta` parameter explained only implicitly through example codes like C25 and B10.

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?

States a specific verb+resource combination: what the official schedule programs for a route on a given day, returning trips per hour and buses on the road. That is concrete and distinct from a history tool, but it never names or excludes siblings such as buses_ruta or historial_ruta, leaving the agent to infer the boundary.

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?

Provides concrete usage contexts via example questions ("¿cuántos viajes tiene el C25 hoy?", "¿a qué hora hay más buses del B10?") and a negative condition ("No necesita historial"), which signals it is the current-schedule tool rather than the historical one. It stops short of explicitly routing the agent to a named alternative tool.

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

Deploy Server

Other Tools