Skip to main content
Glama

Galápagos island-hopping plan

plan_itinerary
Read-onlyIdempotent

Use this when someone wants a day-by-day Galápagos itinerary for a land-based (island-hopping) trip: which islands, how many nights on each, ferry days and what to do each day for a wildlife, snorkelling or budget focus, from arrival at Baltra (GPS) or San Cristóbal (SCY) to departure. Shows a route map card. All inputs are optional. Examples: "Plan 7 days of island hopping in the Galápagos." / "Arma un itinerario de 7 días por las islas 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": "plan_itinerary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays including arrival and departure day (default 7).
focusNowildlife (default), snorkel or budget (free walk-in sites first).
islandsNoIslands to sleep on, 1–3 (default 2). Trips under 5 days use one island, under 7 at most two.
leave_airportNoDeparture airport (default gps).
arrive_airportNogps = Baltra for Santa Cruz (default), scy = San Cristóbal.

Output Schema

NameRequiredDescriptionDefault
daysYes
linkYesPage on galapagosislands.info with these inputs filled in.
inputYes
notesYes
routeYes
nightsYes
summaryYes
day_toursYes
day_tours_pageYes

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 useful behavioral context beyond that: all inputs are optional, and the tool returns a route map card. It does not mention whether results are deterministic for identical inputs despite idempotentHint, a minor gap.

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 scope statement is front-loaded in the first sentence and the map-card note and examples follow logically. The bilingual example utterances add real disambiguation value, though the sentence is long and packs several ideas (islands, nights, ferries, activities, focus, airports) into one run-on stretch.

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?

An output schema exists, so return values need no explanation, and the description covers scope, optionality, and triggering examples for a five-parameter read-only planner. The only omission is the departure airport being independently selectable from arrival, which the description glosses over by listing only arrival options.

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 description coverage is 100%, with defaults and enum meanings documented inline, so the schema does the heavy lifting. The description reinforces the GPS/SCY airport meanings ('from arrival at Baltra (GPS) or San Cristóbal (SCY)') but adds no new per-parameter detail such as how days interact with islands beyond what the schema already states.

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?

States a specific verb and resource: a day-by-day Galápagos itinerary for a land-based, island-hopping trip, including what it covers (islands, nights, ferry days, daily activities, focus). The 'land-based (island-hopping)' qualifier separates it cleanly from cruise-oriented siblings like land_or_cruise and from ferry_board or estimate_trip_cost.

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 wants...' gives an explicit trigger condition, and the land-based qualifier implicitly routes cruise queries elsewhere. It stops short of naming alternatives explicitly (e.g. 'for cost estimates use estimate_trip_cost'), so an agent must infer the routing rather than being told.

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