Skip to main content
Glama

Normas de pesca en Paraguay

normas_de_pesca
Read-only

Devuelve las normas de pesca deportiva de Paraguay tal como las publica la guía: licencia del MADES, tallas mínimas, artes permitidas y cupo, veda anual, medidas extraordinarias vigentes y lo que corre para pescadores extranjeros, con el link a la página de cada tema. Sin tema, devuelve todas.

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

Input Schema

NameRequiredDescriptionDefault
temaNoTema.
idiomaNoIdioma de la respuesta: es (por defecto), en o pt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 meaningful context beyond that: the data mirrors "la guía" as published, and each topic comes with a link to its source page. It does not discuss freshness/caching or rate limits, but for a static read-only reference tool this is solid disclosure.

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 verb and scope are front-loaded and the second sentence cleanly states the default behavior. The middle enumeration is long but each item corresponds to a real topic an agent would query, so nothing is filler; only slight redundancy with the enum values.

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 two-parameter, read-only lookup with no output schema, the description covers what is returned (per-topic regulation content plus source links) and the default scope. The only notable omission is any mention of the idioma response-language option, which an agent must discover from the schema.

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?

With 100% schema coverage the baseline is 3, and the description earns a bump by specifying the omitted-parameter behavior ("Sin tema, devuelve todas"), which the schema does not state since tema is optional. It says nothing about the idioma parameter, but the schema documents that enum and its default clearly.

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?

The description opens with a specific verb and resource ("Devuelve las normas de pesca deportiva de Paraguay") and enumerates the exact content covered: licencia MADES, tallas mínimas, artes y cupo, veda, medidas extraordinarias, extranjeros. This makes it clearly distinct from siblings like info_especie (species data) or nivel_del_rio (river levels), so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"Sin tema, devuelve todas" tells the agent that omitting the filter is a valid, well-defined call and what it yields, which is real usage context. There is no explicit when-not guidance or named alternative, so it falls short of a 5.

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