Skip to main content
Glama

Ficha de una especie

info_especie
Read-only

Devuelve la ficha de una especie de pesca deportiva de Paraguay: nombre en tres idiomas, nombre científico, temporada, técnica, zonas donde se pesca, talla mínima legal y el link a su página. Sin especie, devuelve la lista de las especies de la guía.

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

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

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 value beyond them by disclosing the exact content of the response payload and the behavior change when the species argument is omitted, though it says nothing about invalid species ids or unknown-language handling.

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?

Two sentences, no filler: the first front-loads what is returned, the second states the no-argument behavior. Every clause earns its place by naming a returned field or a calling mode.

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?

There is no output schema, so the description must convey the return shape, and it does so by listing all fields of the species profile plus the list-mode fallback. For a two-parameter read-only lookup with full schema coverage and explicit annotations, nothing an agent needs in order to call it 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 both parameters fully documented including the enum and the accepted id/name forms, so the schema carries the parameter burden. The description adds no syntax or format detail for "especie" or "idioma"; its mention of "nombre en tres idiomas" describes output fields rather than the language-selection parameter, so the baseline 3 applies.

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 states a specific verb and resource ("Devuelve la ficha de una especie de pesca deportiva de Paraguay") and enumerates the exact fields returned: multilingual name, scientific name, season, technique, zones, minimum legal size and page link. It also clarifies the no-argument case returns the species list, which separates it from siblings like normas_de_pesca or listar_zonas.

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?

It gives a clear use condition (fetch one species' profile) and an explicit fallback rule: call without "especie" to get the catalog of species. What is missing is any explicit routing against alternatives — it never says when to prefer normas_de_pesca or listar_zonas instead, leaving that inference to the agent.

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