Skip to main content
Glama

buscar_parada

Read-only

Find TransMilenio stations and SITP stops by name, ignoring accents, and get each stop's ID, type, coordinates, and the routes that serve it.

Instructions

Estaciones de TransMilenio y paraderos del SITP por nombre, sin importar tildes.

Devuelve id, nombre, tipo (estación, vagón o paradero), coordenadas y rutas que paran ahí. Ejemplos: "Calle 72", "Portal Norte", "Ricaurte", "cl 80 kr 30".

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": {
      "nombre": "<nombre>"
    },
    "name": "buscar_parada"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo
nombreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only and open-world behavior, and the description adds real value beyond them: it names the returned fields (id, nombre, tipo, coordenadas, rutas) and discloses accent-insensitive matching plus the possible station/wagon/platform types. It omits that results are capped by the limite parameter, which matters for a fuzzy name search.

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?

Front-loaded with purpose in the first line, then return shape, then concrete examples. Three short lines, no filler, and the examples are directly actionable as query patterns.

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 correctly compensates by enumerating the returned fields and the meaning of 'tipo'. The remaining gap is the undocumented result limit, which leaves the agent unaware that a broad query may return only a subset.

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 carry parameter meaning. It does a good job for nombre — accent-insensitivity and the acceptance of colloquial or abbreviated forms via examples — but says nothing about limite, whose default of 8 silently truncates results.

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 (buscar) and resource (estaciones de TransMilenio y paraderos del SITP) and qualifies the lookup as name-based and accent-insensitive. It implicitly separates itself from location-oriented siblings like paraderos_cerca or buses_cerca, but never names an alternative explicitly.

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 'por nombre' plus sample queries ("Calle 72", "Portal Norte", "cl 80 kr 30"), which shows the expected input style including abbreviations. There is no explicit statement of when to use this versus nearby/location or route-based siblings.

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