Skip to main content
Glama

Nusa Penida Holiday Planner

Reisebedingungen prüfen (Seegang, Wetter, Events, Warnungen)

check_travel_conditions
Read-onlyIdempotent

Prüft für einen Zeitraum die Überfahrtsbedingungen nach Nusa Penida: Wellenhöhe und Wind in der Badung-Straße, Wetter auf der Insel sowie Zeremonien, Feiertage (z.B. Nyepi) und Reisewarnungen. Datenquellen: Open-Meteo (frei) und die penida.de-Eventdatenbank.

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

Input Schema

NameRequiredDescriptionDefault
daysNoAnzahl Tage der Vorschau (1-14, default 7).
from_dateNoStartdatum (default heute).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The description discloses the data sources (Open-Meteo for free weather/wave data, the penida.de event database), which is genuine behavioral context beyond the readOnly/idempotent annotations — it tells the agent where accuracy and coverage come from. It does not describe return format or freshness/latency, so not a 5.

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?

Two well-formed sentences: purpose and dimensions first, then data sources. No wasted wording and it is front-loaded, though the data-source sentence could arguably be trimmed.

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 read-only check tool with no output schema and fully documented parameters, this is largely complete: it says what is checked and where the data comes from. The only gap is the absence of any hint about the shape of the returned conditions.

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%, so both parameters (days and from_date) are already documented in the schema. The description only adds that it operates "für einen Zeitraum," mapping loosely to those fields without adding syntax or default detail. Baseline 3 is appropriate.

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 uses a specific verb ("Prüft") with a clear resource ("Überfahrtsbedingungen nach Nusa Penida") and enumerates the exact dimensions checked: Wellenhöhe/Wind in the Badung-Straße, Wetter, Zeremonien, Feiertage and Reisewarnungen. This clearly separates it from pure-listing siblings like list_events or list_ferries, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for checking crossing conditions over a given period, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no routing to siblings. Acceptable but leaves comparison to the agent.

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