Skip to main content
Glama

Galápagos weather now

live_conditions
Read-onlyIdempotent

Use this when someone asks about the weather or sea temperature in the Galápagos right now or today: air temperature, sky, wind, rain in the next hour and satellite sea surface temperature for Puerto Ayora, Puerto Baquerizo Moreno, Puerto Villamil and Puerto Velasco Ibarra, with the local time. For typical weather in a month use month_guide. Examples: "What's the weather in Puerto Ayora right now?" / "¿Qué tiempo hace ahora 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": "live_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoOne town. Omit for all four.

Output Schema

NameRequiredDescriptionDefault
linkYesPage on galapagosislands.info with these inputs filled in.
townsYes
creditsYes
updatedYes
galapagos_time_nowYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds freshness semantics ('right now or today', 'rain in the next hour') and the fact that local time is included, which is useful beyond the annotations. It says nothing about data staleness, error cases, or what happens when a town has no sensor data, so it adds context without going much past the annotation bar.

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 usage trigger is front-loaded, followed by the data scope, the sibling alternative, and examples. Every sentence carries information, though the opening sentence is long and dense with an embedded list, and the bilingual example pair is slightly redundant for a read-only lookup 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?

The tool is simple: one optional enum parameter, rich annotations, and an output schema that covers return values. The description supplies the freshness, geographic coverage, and sibling routing that the structured fields do not, leaving nothing an agent needs in order to call it correctly.

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 the town enum with 'Omit for all four'. The description restates the four towns by their human-readable names (Puerto Ayora, Puerto Baquerizo Moreno, Puerto Villamil, Puerto Velasco Ibarra), which modestly helps map natural-language town names onto the enum slugs. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description names a specific resource (current weather and sea temperature in the Galápagos) and enumerates exactly what is returned: air temperature, sky, wind, rain in the next hour, satellite sea surface temperature, and local time. It explicitly contrasts itself with month_guide, so an agent can separate real-time conditions from climatological averages without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering condition ('when someone asks about the weather or sea temperature ... right now or today') and names the alternative and its condition ('For typical weather in a month use month_guide'). The coverage of the four supported towns further scopes when the tool applies.

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