Skip to main content
Glama

Nusa Penida Holiday Planner

Aktivitäten & Erlebnisse

list_activities
Read-onlyIdempotent

Listet Aktivitäten (Tauchen, Yoga, Kochkurse, Roller-Verleih, Wanderungen) mit Kategorien-, Preis- und Ratingfiltern.

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_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTrefferzahl (1-50, default 20).
queryNo
offsetNoOffset für Pagination (0-500, default 0).
sort_byNo
categoryNoz.B. 'diving', 'yoga', 'transport'.
max_priceNoHöchstpreis in EUR.
min_priceNoMindestpreis in EUR.
difficultyNo
max_ratingNoHöchst-Rating (0-10).
min_ratingNoMindest-Rating (0-10).

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 readOnlyHint, idempotentHint and openWorldHint=false, so safety behavior is covered by structured data. The description adds the useful fact that the catalog includes rental/transport offerings like Roller-Verleih, but says nothing about defaults, result ordering, or pagination behavior across the 20-item default page.

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 front-loaded sentence with no filler; the parenthetical examples do real work in identifying scope. It is efficient but is a bare one-liner for a tool with ten parameters and no structured context for them.

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?

With ten optional parameters, no output schema and only a single sentence, an agent lacks guidance on pagination limits (1-50 / offset up to 500), sort semantics, and free-text query behavior. Adequate for a browse tool, but the filter surface is only partially explained.

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 70%, so baseline is 3. The description confirms that category, price and rating filters are the intended levers, but it does not mention limit, offset, sort_by, query, or difficulty, leaving five of ten parameters undocumented in the prose.

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?

Specific verb + resource ("Listet Aktivitäten") with a concrete enumeration of the activity types covered (Tauchen, Yoga, Kochkurse, Roller-Verleih, Wanderungen), which implicitly separates it from list_restaurants or list_events. It never names an alternative tool, so routing among list_attractions / search_tours is left to inference.

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?

The description states what can be filtered but gives no when-to-use, when-not-to-use, or alternative guidance, despite several siblings (search_tours, list_attractions, list_events) covering adjacent territory. An agent must guess from the name alone whether to browse here or search elsewhere.

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