Skip to main content
Glama

Cómo llegar y cruzar la frontera

como_llegar
Read-only

Devuelve los pasos de frontera y aeropuertos con control migratorio que sirven para llegar a una zona de pesca (o todos los de un país vecino): qué une cada paso, horario, notas y cierres vigentes, más los pasos que Migraciones tiene inhabilitados, la fecha de la consulta y el link a la página con documentos, auto y vuelta con el pescado.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "como_llegar"
  }
}

Input Schema

NameRequiredDescriptionDefault
zonaNoZona de pesca: id (pilar, pasodepatria, cerrito, ayolas, ciudaddeste, encarnacion, villaflorida, villeta, asuncion, concepcion, vallemi, bahianegra) o nombre.
desdeNoDesde qué país se llega (ar, br, bo) o aire para los aeropuertos.
idiomaNoIdioma de la respuesta: es (por defecto), en o pt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real value beyond them by disclosing that results include current closures, crossings disabled by Migraciones, the query date (data freshness), and a link to the documentation page.

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?

The single dense sentence is front-loaded with the resource and scope, then enumerates the returned fields after a colon. It is content-rich rather than padded, though the long run-on structure slightly reduces scanability.

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

Completeness5/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 carries the burden of describing return values, and it does so thoroughly: what each crossing connects, hours, notes, active closures, disabled crossings, query date, and a documentation link. Nothing an agent needs to decide or call correctly is missing.

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 coverage is 100%, with enums and descriptions for all three parameters, so the baseline is 3. The description adds a little meaning by implying that zona can be omitted to get all crossings of a neighboring country and by framing 'desde' as the origin country or 'aire' for airports, but it does not explain the zona id/name duality further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Devuelve') and resource ('pasos de frontera y aeropuertos con control migratorio'), plus the exact scope: crossings serving a fishing zone or all crossings of a neighboring country. This is clearly distinguishable from siblings like listar_zonas, nivel_del_rio, or normas_de_pesca.

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?

The purpose clause ('que sirven para llegar a una zona de pesca') implies when to use it, and the parenthetical hints that omitting zona returns a country's full list. However, there is no explicit when-not-to-use guidance and no named alternative tool, so usage must be inferred from scope.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources