Skip to main content
Glama

paraderos_cercanos

Read-onlyIdempotent

Find SITP and TransMilenio stops or stations within a chosen radius of a latitude and longitude for nearby transit access.

Instructions

Paraderos y estaciones a menos de radio_m metros de una coordenada (máx. 2000 m).

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_cercanos"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
limiteNo
radio_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds a genuine constraint not present in the schema: radio_m is capped at 2000 m. It says nothing about result ordering, how limite truncates results, or what happens when the radius is exceeded.

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?

A single punchy sentence with the resource front-loaded and the constraining detail (max radius) trailing. Nothing is redundant and every clause adds information.

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 four-parameter read-only lookup with annotations covering safety and no output schema, the description gives the essential concept and the key numeric constraint. The remaining gap is limite and the shape of returned results, which is minor but not negligible.

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 (units in meters and a 2000 m maximum) and implies lat/lon as a coordinate pair. The limite parameter, including its default of 15 and its effect on the result set, is left entirely unexplained.

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 names the resource (paraderos y estaciones) and the operation (those within radio_m meters of a coordinate), so an agent knows this is a proximity search rather than a name lookup. It does not explicitly distinguish itself from the sibling buscar_paraderos, but 'cercanos' plus the coordinate-based framing makes the distinction inferable.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as buscar_paraderos for name-based lookup. The only implicit cue is the geographic framing, which the agent must infer on its own.

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