Skip to main content
Glama

Nusa Penida Holiday Planner

Sehenswürdigkeiten auf Nusa Penida

list_attractions
Read-onlyIdempotent

Listet Strände, Aussichtspunkte und Sehenswürdigkeiten mit Kategorie-, Orts- und Rating-Filtern.

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

Input Schema

NameRequiredDescriptionDefault
limitNoTrefferzahl (1-50, default 20).
queryNo
offsetNoOffset für Pagination (0-500, default 0).
sort_byNo
categoryNoz.B. 'beach', 'viewpoint', 'temple', 'waterfall'.
locationNoRegion (z.B. 'Ost', 'West', 'Nord', 'Süd').
max_ratingNoHöchst-Rating (0-10).
min_ratingNoMindest-Rating (0-10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on result volume, default page size, or whether filters combine as AND — so it contributes little extra behavioral context.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity leaves no room for routing or behavior hints that would have earned their place.

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 8-parameter read-only list tool with no output schema, the definition covers the what but omits pagination behavior, sorting options, free-text query, and default result count — all of which the agent must discover from the schema alone. Adequate but with clear gaps.

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 description echoes the category, location and rating filter concepts already documented in the schema at 75% coverage, adding no new meaning such as filter combination rules or rating scale interpretation. The undocumented parameters (query, sort_by) get no help from the description either, which is the expected baseline case.

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 gives a concrete verb plus a resource ('Listet Strände, Aussichtspunkte und Sehenswürdigkeiten') and names the filter axes, so an agent knows it is a filtered attraction listing rather than a generic catalog. It does not explicitly distinguish itself from siblings such as list_activities or list_restaurants, which keeps it out of 5 territory.

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: the agent can infer this is the tool for browsing attractions with category/location/rating constraints. There is no statement of when to prefer it over list_activities, search_tours, or plan_trip, and no exclusions or prerequisites.

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