Skip to main content
Glama

buscar_paraderos

Read-onlyIdempotent

Find SITP stops and TransMilenio stations by name, code, or ID, returning coordinates, stop type, and serving routes.

Instructions

Busca paraderos SITP y estaciones de TransMilenio por nombre, código o id.

Devuelve id, nombre, tipo (estación / paradero), coordenadas y las rutas que paran ahí. Ejemplos: "Banderas", "Portal Américas", "Cll 72", "064A08_TM".

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": {
      "texto": "<texto>"
    },
    "name": "buscar_paraderos"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoYes
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile carries itself. The description adds real context beyond that: it enumerates the return fields (id, nombre, tipo, coordenadas, rutas) and the two entity kinds covered (estación / paradero). It does not state matching/fuzzy-search behavior or pagination semantics for the limit.

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?

Three short lines, front-loaded with the action and scope, then the return shape, then input examples. Given the empty parameter descriptions, the examples earn their place rather than padding.

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?

No output schema exists, and the description correctly fills that gap by naming exactly what is returned. For a simple two-parameter read search this is close to complete; only the behavior of 'limite' and matching strictness remain unstated.

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 must compensate. It does well for the required 'texto' parameter by declaring it accepts name, code, or id and giving four concrete examples. However, the 'limite' parameter is never mentioned, so its meaning (result cap, default 10) is left entirely unexplained despite being the second of only two parameters.

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 (busca) and resource (paraderos SITP y estaciones de TransMilenio) plus the three matching keys (nombre, código, id). This implicitly separates it from proximity-based siblings like paraderos_cercanos, but no sibling or alternative is named explicitly, so it falls short of full differentiation.

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 only implied: agent must infer that this is the tool for a known name/code and that geographic lookup belongs elsewhere. The worked examples ("Banderas", "Portal Américas", "Cll 72", "064A08_TM") help show the input forms but are not explicit when/when-not guidance or exclusions.

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