Galapagos Trip Planner

Galápagos visitor site

visitor_site

Read-onlyIdempotent

Use this for a named Galápagos visitor site or to list the main ones by island: Kicker Rock, Tortuga Bay, Las Grietas, North Seymour, Bartolomé, Los Túneles, Sierra Negra and others. Returns how to get there (walk-in or boat tour), duration, best months and what you see. Examples: "How do I get to Kicker Rock?" / "¿Cómo llego a Las Grietas?"

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

Input Schema

Name	Required	Description	Default
`site`	No	One site. Omit to list them.
`island`	No	Only sites reached from this island.

Output Schema

Name	Required	Description
`link`	Yes	Page on galapagosislands.info with these inputs filled in.
`count`	Yes
`sites`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already disclose that this is a read-only, idempotent, non-destructive lookup, so the safety profile is covered. The description adds useful behavioral detail by saying the tool returns access method, duration, best months, and wildlife, which tells the agent what kind of information to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary use case, followed by a compact list of examples and return content. Every sentence contributes useful context, and the examples are directly relevant to how an agent would invoke the tool.

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 simple, read-only lookup with two fully described enum parameters and an output schema, the description supplies enough purpose, usage context, example phrasing, and expected return content. Nothing essential for correct invocation 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 description coverage is 100%, and the schema already documents that 'site' is one site with omission meaning list mode, and that 'island' restricts to sites reached from that island. The description reinforces those ideas but adds no new parameter-level semantics beyond the schema.

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?

The description states a specific resource (Galápagos visitor sites) and two clear modes: look up a named site or list sites by island. It names representative sites and gives concrete examples, but it does not explicitly distinguish itself from related siblings such as find_wildlife or month_guide.

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?

It clearly says to use this for a named site or for listing the main ones by island, and supplies example queries that make the intended use concrete. It does not state when to use an alternative sibling tool or any exclusions.

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?