Skip to main content
Glama

Nusa Penida Holiday Planner

Zeremonien, Festivals & Reisehinweise

list_events
Read-onlyIdempotent

Listet balinesische Zeremonien, saisonale Hinweise und Reisewarnungen mit Datumsrange, Kategorie, Ort und Tag-Filter.

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

Input Schema

NameRequiredDescriptionDefault
tagNoEinzelnes Tag, z.B. 'manta', 'galungan', 'sicherheit'.
limitNoTrefferzahl (1-50, default 20).
offsetNoOffset für Pagination (0-500, default 0).
sort_byNo
to_dateNoEnddatum (default: heute +90 Tage).
categoryNo
locationNo
from_dateNoStartdatum (default: heute).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, closed-world read, so the safety profile needs no repetition. The description adds the content scope (ceremonies, seasonal notes, alerts) but says nothing about result ordering, default window behaviour, or how many results to expect beyond what the schema states.

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?

One tightly packed sentence with the resource scope front-loaded and no filler. It could be slightly improved by leading with the primary use case (ceremonies/festivals) rather than mixing in alerts.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter, read-only listing tool with no output schema, the definition covers what is retrieved and by which filters, but leaves ambiguous whether alerts here duplicate the dedicated travel-condition tool. That ambiguity matters for correct tool selection.

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?

The schema covers 63% of the eight parameters, including defaults for from_date/to_date, limits and the tag example. The description restates the filter axes (date range, category, location, tag) but adds no semantics for sort_by, limit or offset, so it is roughly at the baseline for moderate schema coverage.

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?

A concrete verb ('Listet') plus enumerated resources: Balinese ceremonies, seasonal notes and travel alerts. It is clear what the tool returns. It does not explicitly distinguish itself from siblings such as list_travel_tips or check_travel_conditions, which overlap with 'Reisewarnungen'.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no mention of alternatives. An agent facing both list_travel_tips and check_travel_conditions has to guess whether this list tool is the right entry point for travel alerts.

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