Galapagos Trip Planner

Galápagos month by month

month_guide

Read-onlyIdempotent

Use this when someone asks about the Galápagos in a given month or the best time to visit: air and sea temperature, typical rain, sea state and ferry seasickness level, crowds, wetsuit advice, and what the wildlife is doing that month (albatross, booby courtship, turtle nesting, whale and hammerhead season and more). Examples: "What is the Galápagos like in August?" / "¿Cómo está el clima en Galápagos en agosto?"

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

Input Schema

Name	Required	Description	Default
`month`	No	Month as 1–12 or an English month name. Default: the current month in the Galápagos.

Output Schema

Name	Required	Description
`link`	Yes	Page on galapagosislands.info with these inputs filled in.
`month`	Yes
`sea_c`	Yes
`crowds`	Yes
`events`	Yes
`season`	Yes
`wetsuit`	No
`air_low_c`	Yes
`rain_days`	Yes
`sea_state`	Yes
`air_high_c`	Yes
`year_round`	No
`climate_basis`	No
`rain_mm_typical`	Yes
`sea_rank_warmest`	No
`seasonal_wildlife`	Yes
`ferry_seasickness_level`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real value beyond that by specifying the breadth of content returned (climate, sea state, crowds, gear, wildlife phenology), which is the main thing an agent needs to judge relevance; only pagination/units remain unstated and the output schema covers returns.

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 trigger is front-loaded in the first clause, followed by a content list and two illustrative queries. The content list is long but each item maps to a distinct thing the agent may need to answer, so the length is largely earned; trimming the 'and more' tail would tighten it slightly.

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?

For a one-optional-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs to route and call it: trigger, content scope, language support, and month handling. Nothing material 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% and the parameter already documents the 1–12 / English-month-name formats and the current-month default, so little is left to add. The description's mention of 'a given month' and its Spanish example only loosely reinforce that idea; it adds no new syntax or edge-case guidance beyond the schema.

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?

A specific verb-plus-resource: it returns month-by-month Galápagos conditions, enumerated concretely (air/sea temperature, rain, sea state, ferry seasickness, crowds, wetsuit advice, wildlife activity). That enumeration clearly separates it from siblings like live_conditions (current) and find_wildlife (species lookup).

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 clause gives an explicit trigger — someone asking about the Galápagos in a given month or the best time to visit — plus two sample queries in English and Spanish. It doesn't name the sibling alternatives (live_conditions for present-day data, find_wildlife for species detail), so the when-not boundary is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Galapagos Trip Planner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?