Skip to main content
Glama

buses_cerca

Read-only

Find live TransMilenio buses within 50–5000 m of a coordinate, ordered from nearest to farthest. Set radius and limit to see what is currently on the street around a point.

Instructions

Buses en vía alrededor de un punto (radio de 50 a 5000 m), del más cercano al más lejano.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "buses_cerca"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
limiteNo
radio_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world nature, so the description adds value by disclosing two traits the schema does not: the hard radius floor/ceiling of 50–5000 m and the result ordering nearest-to-farthest. It does not say how many results come back by default or whether positions are live vs. scheduled, which would have pushed this higher.

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?

A single front-loaded sentence with the resource first and the constraints parenthesized; nothing is padded or repeated. It is a bit compressed – the parenthetical mixes units, bounds, and ordering – but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter geospatial query with no output schema and zero schema descriptions, the definition says nothing about the response shape, the meaning of 'en vía' (in-service vs. scheduled), or how limite interacts with the radius. An agent can call it, but cannot predict what comes back.

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

Parameters2/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, yet it only clarifies radio_m (bounds) and the implied sort order. lat/lon are self-evident, but limite (default 30, clearly a cap on results) is never explained, leaving a quarter of the parameters undocumented anywhere.

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 concrete resource (buses en vía) plus a spatial scope (around a point) and an ordering (nearest to farthest), so an agent can tell it apart from a route-level tool like buses_ruta. It stops short of naming a sibling to contrast with, but the verb+resource+scope is unambiguous.

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?

Use is implied by 'alrededor de un punto' – it is clearly a proximity query – and the 50–5000 m window bounds when it is applicable. However, there is no explicit 'use this instead of X' guidance versus paraderos_cerca (stops near a point) or llegadas, so the agent must infer the boundary between them.

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