Skip to main content
Glama

Bestiario

ver_especie

Read-onlyIdempotent

Muestra la ficha completa de una especie: descripción, hábitat, dieta, respuesta del servidor y visitas por hora de Buenos Aires.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nombre": "<nombre>"
    },
    "name": "ver_especie"
  }
}

Input Schema

NameRequiredDescriptionDefault
nombreYesNombre de la especie, por ejemplo "Cazador de .env" o "Mozlila".

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 readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is lighter. It still adds real value by disclosing the return payload's composition (description, habitat, diet, server response, hourly visits), which matters because no output schema exists. It omits failure behavior for unknown species names.

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?

One front-loaded sentence that moves straight from the action to the returned fields, with no filler. The field enumeration is slightly idiosyncratic but earns its place given the absence of an output schema.

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 one-parameter read tool with full annotation coverage and no output schema, the definition covers both what it does and roughly what comes back. The only missing piece an agent would want is error/empty-case behavior for unrecognized species names.

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% and the single parameter already carries an example ("Cazador de .env" / "Mozlila"). The description adds no further meaning about name matching, casing, or accepted aliases, so the baseline of 3 applies.

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?

States a specific verb and resource ("Muestra la ficha completa de una especie") and enumerates the content of that record, so an agent can tell it retrieves one species' detail rather than a listing like listar_especies. It never names a sibling explicitly, so differentiation is inferred from the singular resource.

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?

Usage is only implied: the singular "una especie" plus the required name parameter suggests detail lookup after a listing, but there is no explicit when-to-use, no exclusion, and no mention of what happens if the species does not exist.

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