Skip to main content
Glama

Listar las zonas de pesca

listar_zonas
Read-only

Devuelve las zonas de pesca de la guía sobre los ríos de Paraguay, con su departamento, río, qué las distingue, qué especies se pescan, cuántos prestadores hay por rubro y el link a su página. Con una especie, devuelve solo las zonas donde se pesca.

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

Input Schema

NameRequiredDescriptionDefault
idiomaNoIdioma de la respuesta: es (por defecto), en o pt.
especieNoEspecie: id (dorado, surubi, pacu, pira-pyta, boga, tararira, pati, pirana) o nombre en español, inglés o portugués.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 the safety profile is covered. The description adds value by listing the exact fields returned (departamento, río, distinguishing features, species, provider counts, page link) and clarifying the conditional filtering behavior with 'especie'. It does not mention pagination or rate limits, but those are minor for this read-only list tool.

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?

The description is two sentences, front-loaded with the main purpose and output fields, followed by the filtering condition. Every sentence earns its place, with no redundant or vague wording.

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?

There is no output schema, so the description carries the burden of explaining return values, which it does by listing the included fields. It also clarifies the optional species filter. For a simple read-only listing tool, this is nearly complete, though it omits any note on result ordering, pagination, or limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema for the 'especie' parameter by stating that supplying a species filters results to zones where that species is fished. The 'idioma' parameter is not discussed in the description, but the schema fully documents it, so this is still an improvement over the baseline.

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 states a specific verb and resource: 'Devuelve las zonas de pesca de la guía sobre los ríos de Paraguay'. It also enumerates the returned fields (departamento, río, qué las distingue, especies, prestadores, link), making the tool's output clear. It does not explicitly differentiate itself from sibling tools like buscar_prestadores or info_especie, so a 4 rather than 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?

The description explains a filtering behavior ('Con una especie, devuelve solo las zonas donde se pesca'), but it gives no explicit guidance on when to use this tool versus alternatives. It does not name any sibling tool or state exclusions, so the agent must infer usage from the tool name and context.

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