Skip to main content
Glama

proximas_paradas

Read-only

Tracks a TransMilenio bus by bus number or plate and returns its next stops with estimated arrival times.

Instructions

Por dónde va un bus y sus próximas paradas con hora estimada.

bus: el número pintado en el bus ("E0001", "Z70-4428") o la placa. llegadas y buses_ruta devuelven ese número.

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": {
      "bus": "<bus>"
    },
    "name": "proximas_paradas"
  }
}

Input Schema

NameRequiredDescriptionDefault
busYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.6/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 that results include an estimated time and reflect current progress along the route, but it does not say whether the estimate is real-time or scheduled, how stale it may be, or what is returned when the bus is out of service or not found.

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 first sentence front-loads purpose and output in one line; the second is a compact parameter note with examples. Nothing is redundant, though the reference to llegadas and buses_ruta is packed into the parameter note without framing it as a workflow step.

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 single-parameter read tool with annotations covering safety and no output schema to explain, the definition covers purpose, input source, and expected return content in two sentences. The remaining gap is live-versus-scheduled semantics of the ETA, which matters for a real-time transit lookup but is a modest omission.

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%, so the description must carry the parameter, and it does: `bus` accepts either the painted fleet number (with concrete examples like "E0001", "Z70-4428") or the license plate, and it names the sibling tools that return that identifier. That is meaningful guidance beyond a bare string field, though the accepted format of plates is not spelled out.

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 states a specific resource and outcome: where a bus currently is plus its upcoming stops with estimated arrival times. That is clearly distinguishable from a pure arrivals tool, but it does not explicitly contrast itself with siblings such as llegadas or historial_ruta, which it only references as sources of the bus identifier.

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 rather than stated: an agent learns to call llegadas or buses_ruta first to obtain the bus number and then call this tool for live position and next stops. There is no explicit when-not-to-use case, no mention of alternatives for route-level vs stop-level queries, and no stated failure behavior for an unknown bus.

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