Skip to main content
Glama

Galápagos trip cost

estimate_trip_cost
Read-onlyIdempotent

Use this when someone wants to know what a Galápagos trip costs or needs a budget. Adds up the national park fee, transit control card, return flight from Quito or Guayaquil, an optional airport hotel night, hotels or a cruise, ferries, water taxis, the Isabela dock fee, day tours and food for the given days, travellers, style and islands. Returns every line, the total, per person and per person per day in US dollars, and shows a printed receipt card. All inputs are optional. Examples: "What does 8 days in the Galápagos cost for two people?" / "¿Cuánto cuesta un viaje de 8 días a Galápagos para dos personas?"

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

Input Schema

NameRequiredDescriptionDefault
daysNoDays in the Galápagos (default 7).
modeNoland (hotels and day tours, default) or cruise (live aboard).
styleNobudget, mid (default) or upper (comfort hotels, luxury cruise).
toursNoLand only: guided day tours per person (default 3).
adultsNoAdults, 12 and over (default 2).
islandsNoLand only: islands to sleep on, 1–3 (default 2: Santa Cruz and Isabela).
childrenNoChildren under 12 (default 0).
fly_fromNoMainland airport for the flight to the islands (default quito).
nationalityNoPark fee group: foreign (default), canmercosur (CAN or Mercosur national) or resident (Ecuadorian or resident).
mainland_nightNoAdd a hotel night near the mainland airport before the flight (default true).

Output Schema

NameRequiredDescriptionDefault
linkYesPage on galapagosislands.info with these inputs filled in.
inputYes
linesYes
totalYes
checkedYes
currencyYes
per_personYes
assumptionsYes
per_person_per_dayYes

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, closedWorldHint and non-destructive, so safety needs no restating. The description goes beyond them by enumerating exactly which cost components are summed (park fee, transit control card, return flight, dock fee, water taxis, day tours, food), stating "All inputs are optional", and giving the currency and breakdown granularity — real behavioral context an agent cannot get from the annotations.

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?

Usage condition is front-loaded, then the inclusion list, then the return contract, then examples — a sensible order with no filler sentences. The middle enumeration of cost components is long and reads like a laundry list, but each item genuinely tells the agent what the price covers, so the bulk mostly earns its place.

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 10-parameter, all-optional estimator with a full schema and an output schema, the description is comfortably sufficient: it establishes trigger, computation basis, and return contract, and explicitly notes that no input is required. Minor omissions — no mention of the 3–15 day bound or the land-only scope of tours/islands — are already covered in the schema descriptions.

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?

With schema description coverage at 100% and enums on mode, style, fly_from and nationality, the schema already carries defaults and allowed values. The description only loosely gestures at the inputs ("days, travellers, style and islands") and adds a little meaning by mapping cost components to parameter groups, but supplies no syntax, format or interaction detail beyond what is already structured.

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?

"Adds up ... for the given days, travellers, style and islands" is a specific verb-plus-resource statement, and "Returns every line, the total, per person and per person per day in US dollars" pins down the output shape. No sibling (entry_rules, ferry_board, find_wildlife, plan_itinerary) does cost estimation, so the tool is trivially distinguishable from its neighbors.

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?

"Use this when someone wants to know what a Galápagos trip costs or needs a budget" gives a clear triggering condition plus two worked example queries, including a Spanish one. It stops short of naming a when-not case or pointing at a sibling (e.g., plan_itinerary when the user needs an itinerary rather than a price), so it is strong but not fully routing.

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