Skip to main content
Glama

Buscar prestadores de pesca

buscar_prestadores
Read-only

Busca en el directorio de Pira Experience (lodges de pesca, guías, alojamientos, barcos hotel, embarcaciones, excursiones, tiendas de pesca y torneos de Paraguay) por zona, categoría, especie que se pesca en su zona, idioma en que atienden o texto libre. Devuelve hasta 20 prestadores (nombre, rubro, zona, precio orientativo o Consultar, idiomas, puntaje de Google si lo hay y link a la ficha, donde está su contacto) y el total encontrado. No da teléfonos ni mails.

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

Input Schema

NameRequiredDescriptionDefault
zonaNoZona de pesca: id (pilar, pasodepatria, cerrito, ayolas, ciudaddeste, encarnacion, villaflorida, villeta, asuncion, concepcion, vallemi, bahianegra) o nombre.
textoNoTexto libre sobre nombre o descripción: pensión completa, kayak, camping...
idiomaNoIdioma de la respuesta: es (por defecto), en o pt.
especieNoEspecie: deja los prestadores de las zonas donde se pesca. Id o nombre.
categoriaNoRubro.
atiende_enNoSolo los que dicen atender en portugués o en inglés.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral context beyond them: a hard cap of 20 results, the returned fields, the 'Consultar' price case, and the notable limitation that phones and emails are not returned and contact lives in the ficha link. The one thing it doesn't say is what happens when more than 20 match (no pagination hint).

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?

Two dense sentences, front-loaded with the action and directory scope, then the return contract. The long parenthetical category list is somewhat heavy but each clause (filters, 20-cap, returned fields, no contact data) carries information an agent needs.

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 describing the return shape, the result cap, the total count, and the exclusion of phone/email. Only the overflow/pagination behavior and how to obtain valid zone or species ids remain unspecified.

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 per-field descriptions, so the schema carries the parameter burden and baseline 3 applies. The prose mostly restates the filters, and it slightly blurs semantics: it describes searching by 'idioma en que atienden', which corresponds to atiende_en, while the `idioma` parameter actually controls response language — a distinction the description does not clarify.

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 concrete verb and resource ('busca en el directorio de Pira Experience') and enumerates the covered rubros (lodges, guías, barcos hotel, tiendas, torneos), plus the exact filter axes. This makes it clearly distinct from the sibling tools (zone listing, species info, river level, regulations, directions) without needing to name them.

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 description makes the use case obvious (directory search with filters) but gives no explicit when-to-use/when-not guidance or routing to alternatives, e.g. whether listar_zonas should be called first to obtain valid zone ids. Usage is implied rather than stated.

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