Skip to main content
Glama

paraderos_cerca

Read-only

Find the nearest TransMilenio stops and stations to a coordinate, including distance and available routes.

Instructions

Estaciones y paraderos con servicio más cercanos a un punto, con distancia y rutas.

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

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
limiteNo
radio_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context by saying results include distance and routes, but it does not explain ranking, what happens when no stops fall within range, or how radius and result limits affect behavior.

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?

It is a single compact sentence with the core purpose front-loaded and no filler. Brevity is appropriate, though the space saved is not used to clarify parameters or sibling choice.

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

Completeness3/5

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

For a simple geographic lookup this covers the essential idea and even indicates the return contents. However, with no output schema and zero parameter descriptions, the lack of detail on coordinates, radius, and limit leaves meaningful gaps.

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% for all four parameters, so the description must compensate but does not. It never mentions lat/lon, the default result limit of 6, or the default 800-meter radius, leaving the agent to infer these entirely from bare schema fields.

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 clearly states the resource (stations and stops with service) and the operation (find the nearest to a point), and it mentions that distance and routes are included. It does not explicitly distinguish itself from siblings such as buscar_parada or proximas_paradas, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives no explicit guidance on when to use this tool versus alternatives like buscar_parada or proximas_paradas. The word 'cerca' implies a proximity search, but there are no conditions, exclusions, or fallback behavior described.

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