Skip to main content
Glama

Nusa Penida Holiday Planner

Fährverbindungen nach Nusa Penida

list_ferries
Read-onlyIdempotent

Listet Fährverbindungen mit Filtern nach Abfahrts-/Zielort, Preis und Betreiber, sortierbar und paginierbar.

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

Input Schema

NameRequiredDescriptionDefault
toNoZielort, z.B. 'Nusa Penida', 'Lembongan'.
fromNoAbfahrtsort, z.B. 'Sanur', 'Kusamba', 'Padang Bai'.
limitNoTrefferzahl (1-50, default 20).
offsetNoOffset für Pagination (0-500, default 0).
sort_byNo
operatorNoBetreiber, z.B. 'Maruti', 'Idola', 'El Rey'.
max_priceNo
min_priceNo

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=true, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered and the description correctly stays consistent with it. The description only adds that results are sortable and paginable; it says nothing about defaults, empty-result behavior, or what a ferry record contains.

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 the resource first and the filter/sort/pagination capabilities after it; no filler. It is slightly dense as a comma-accumulated list but nothing is wasted.

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, all-optional list tool with no output schema, the description covers the filtering dimensions but omits default page size behavior, what fields come back, and whether results are ordered by default. Adequate to invoke, not complete enough to predict the response.

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 63%, with descriptions missing for sort_by, max_price and min_price. The description partly compensates by naming price and sorting as filter/sort dimensions, but it adds no syntax, units, default values, or interaction rules (e.g. min_price vs max_price) beyond what the schema already states.

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 ('Listet') and a concrete resource ('Fährverbindungen') plus the filter dimensions (Abfahrts-/Zielort, Preis, Betreiber) and sorting/paging. The resource is distinctive enough that an agent can separate it from list_activities or list_attractions without opening the schema, though no sibling is named explicitly.

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 sentence enumerates capabilities but never says when to choose this tool, when not to, or what the alternative is for related needs (e.g. search_tours, get_best_price). An agent must infer the ferry-route-search use case purely from the resource noun.

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