Skip to main content
Glama

Galápagos wildlife finder

find_wildlife
Read-onlyIdempotent

Use this when someone asks where or when to see an animal in the Galápagos (giant tortoise, marine or land iguana, sea lion, blue-footed, red-footed or Nazca booby, penguin, flightless cormorant, frigatebird, Darwin's finches, green turtle, Sally Lightfoot crab, flamingo, whitetip reef shark, fur seal, waved albatross, hammerhead, red-lipped batfish), or which animals they can see in a month or around an island. Returns the odds, best months, sites with how to reach them, a fun fact and the Big 15 bingo card. Examples: "Where can I see penguins in the Galápagos?" / "¿Dónde puedo ver piqueros de patas azules en Galápagos?"

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

Input Schema

NameRequiredDescriptionDefault
monthNoOnly animals at their best in this month (1–12 or a month name).
islandNoOnly animals seen on or around this island.
speciesNoOne animal. Omit to list all.

Output Schema

NameRequiredDescriptionDefault
linkYesPage on galapagosislands.info with these inputs filled in.
countYes
filtersYes
speciesYes
bingo_cardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing what comes back: odds, best months, sites with how to reach them, a fun fact and the Big 15 bingo card.

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?

Front-loaded with the when-to-use clause and kept to two sentences before the examples. The long species parenthetical is verbose but earns its place by supporting free-text query matching; the bilingual examples are a small bonus rather than padding.

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 an output schema, full annotation coverage and 100% parameter descriptions, the description carries only the remaining burden of usage framing, which it does well. The one gap is that it never explains how the three optional filters interact when combined.

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 both filters have enum constraints, so the schema already exhausts parameter meaning. The description only restates the filters in prose ('in a month or around an island') without adding semantics such as whether month, island and species combine or how month names are accepted. 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?

Names a specific verb and resource (find wildlife in the Galápagos) and enumerates the covered animals, so an agent can tell it apart from siblings like 'visitor_site' or 'month_guide' without opening a schema. The parenthetical species list also makes query-to-tool matching unambiguous.

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?

The opening 'Use this when someone asks where or when to see an animal...' plus two concrete bilingual example queries gives clear trigger conditions. It stops short of naming when to prefer a sibling such as 'month_guide' for general seasonality, so routing is implied rather than explicit.

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