Skip to main content
Glama

Nusa Penida Holiday Planner

Restaurants & Warungs auf Nusa Penida

list_restaurants
Read-onlyIdempotent

Listet Restaurants mit Küchen-, Preislevel-, 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_restaurants"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTrefferzahl (1-50, default 20).
queryNo
offsetNoOffset für Pagination (0-500, default 0).
cuisineNoz.B. 'indonesisch', 'seafood', 'vegan', 'western'.
sort_byNo
locationNo
max_ratingNoHöchst-Rating (0-10).
min_ratingNoMindest-Rating (0-10).
price_rangeNoPreisniveau von $ (günstig) bis $$$$ (Fine Dining).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 the safety profile is covered and the bar is lower. The description adds nothing behavioral beyond that — no default sort order, no note on how pagination behaves, no indication of result shape or whether an empty filter set returns everything. It does not contradict the annotations, but it contributes little new 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 terseness borders on under-specification for a nine-parameter tool rather than being a model of concision.

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 tool with nine optional parameters, no output schema and no required fields, one sentence is thin: it omits what is returned, how results are ordered by default, what query matches against, and how limit/offset interact. The annotations cover safety but not the operational details an agent needs to call this correctly.

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 67%, so the schema already documents most parameters including ranges and enums. The description groups four filter families (cuisine, price level, location, rating) which maps onto cuisine, price_range, location and min/max_rating, but it says nothing about limit, offset, query or sort_by, leaving the pagination and free-text search semantics entirely to the schema.

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 specific verb plus resource ("Listet Restaurants") and names the filter dimensions, which is enough to distinguish it from list_activities, list_attractions and search_hotels by resource alone. It stops short of explicitly contrasting itself with any sibling, so it is clear but not maximally differentiated.

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 mention of cuisine, price, location and rating filters suggests the tool is for filtered restaurant discovery, but there is no statement of when to prefer it over search_hotels or plan_trip, and no exclusions or prerequisites. An agent can infer the use case from the name and filters, but nothing is stated explicitly.

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