Skip to main content
Glama

Nusa Penida Holiday Planner

Nusa-Penida-Reise planen

plan_trip
Read-onlyIdempotent

Erstellt einen Tagesplan für Nusa Penida (1–7 Tage) inklusive Fähre, Unterkunft, Touren und Sehenswürdigkeiten – mit Preisen und Quell-URLs auf penida.de.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": "<days>"
    },
    "name": "plan_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesAufenthaltsdauer in Tagen (1-7).
budgetNoBudgetniveau, default 'mid'.
interestsNoInteressen zur Gewichtung der Touren.
from_locationNoAbfahrtsort auf Bali, z.B. 'Sanur'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world behavior, so the bar is lower. The description does add useful context that the plan includes prices and source URLs on penida.de, but it says nothing about how the plan is generated, its reliability, or what happens when interests/budget are omitted.

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?

A single well-formed sentence with no filler, front-loading the action and the deliverable. Everything after the dash adds scope rather than padding.

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 four-parameter, output-schema-less tool the description is largely sufficient: it states the output's content (plan plus prices and source URLs) and the day range. It does not explain how the resulting plan is structured or how the optional inputs change it.

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%, so the schema already documents all four parameters including enums and defaults. The description only echoes the 1–7 day range and adds no meaning about how budget or interests weight the resulting tours, so baseline 3 applies.

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?

Names a specific verb and resource: 'Erstellt einen Tagesplan für Nusa Penida', with scope (1–7 Tage) and contents (Fähre, Unterkunft, Touren, Sehenswürdigkeiten). It clearly contrasts with the sibling list_* tools by producing a combined day plan, 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 it should call this when a user wants a full itinerary rather than individual lookups. There is no explicit when-to-use/when-not statement and no pointer to alternatives such as list_ferries or search_tours for single-item requests.

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