Skip to main content
Glama

Nusa Penida Holiday Planner

Reisetipps für Nusa Penida

list_travel_tips
Read-onlyIdempotent

Reisetipps mit Freitext-, Kategorie- und Tag-Filter, Priorisierung und Pagination.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
limitNoTrefferzahl (1-50, default 20).
queryNo
offsetNoOffset für Pagination (0-500, default 0).
sort_byNo
categoryNoz.B. 'anreise', 'geld', 'sim', 'sicherheit', 'roller'.
min_priorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 needs no restating. The description adds that results can be prioritized and paginated, which is some useful behavioral context, but it says nothing about result ordering defaults, total counts, or what an empty filter set returns.

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 compact sentence with the filter capabilities front-loaded and no filler. It is efficient, though its telegraphic style drops needed detail rather than excess words.

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

Completeness2/5

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

For a 7-parameter tool with under-half schema coverage and no output schema, the one-line description is too thin. An agent gets no help on enum semantics, defaults, priority range meaning, or result shape, which is exactly where the schema is silent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 43% across 7 parameters, so the description must carry meaning, but it only loosely restates the obvious filter parameters. It leaves the sort_by enum ('priority_desc' vs 'recent') unexplained and leaves 'Priorisierung' ambiguous between sorting and the min_priority threshold, so the two most easily misused parameters stay unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Reisetipps') and its filter dimensions (Freitext, Kategorie, Tag) plus sorting and pagination, so an agent can tell roughly what comes back. However, there is no explicit verb (list/search/return) and no differentiation from siblings such as list_activities or search_blog_insights, which also return topical content.

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 guidance is given: nothing says when to call this instead of search_blog_insights or plan_trip, and no prerequisites or exclusions are stated. Usage is only implied by the mention of filters.

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