Skip to main content
Glama

info_ruta

Read-onlyIdempotent

Look up SITP/TransMilenio route details by bus code, including path, first and last bus times, frequency, and route type; returns one result per direction or variant.

Instructions

Recorrido, horario (primer y último bus, frecuencia) y tipo de una ruta.

ruta es el código que aparece en el bus: "B72", "G12", "1-1", "H75", "K635"... Las rutas zonales en pareja se encuentran por cualquiera de sus dos códigos. Devuelve un elemento por sentido o variante de la ruta.

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

Input Schema

NameRequiredDescriptionDefault
rutaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral value: it states the return granularity ('un elemento por sentido o variante de la ruta') and that paired zonal routes resolve via either code, neither of which is in the annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short lines ordered purpose → parameter → edge case → return shape, with zero filler. Every sentence carries information the agent could not get from the structured fields.

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 must say something about what comes back, and it does (one element per direction/variant). Purpose, input semantics, and aliasing are all covered for a simple one-parameter lookup. It omits the format of the schedule fields, a minor gap rather than a blocking one.

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 coverage is 0% and the schema only says 'Ruta', so the description carries the full burden. It defines the parameter as the code painted on the bus, supplies five concrete example formats ('B72', 'G12', '1-1', 'H75', 'K635'), and documents the paired-zonal-route aliasing rule. Only exactness details such as case sensitivity or leading-zero handling are left unstated.

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 first sentence names the resource and the exact facets returned: 'Recorrido, horario (primer y último bus, frecuencia) y tipo de una ruta.' That is a specific, concrete purpose an agent can act on. It does not explicitly contrast itself with siblings like rutas_en_paradero or proximos_buses, 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 implied by the parameter explanation — the tool takes the route code printed on the bus, with examples — but there is no explicit 'use this when' or 'use X instead for arrival times/stop lookup'. An agent can infer the fit, but the definition does not route it away from siblings.

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