Skip to main content
Glama

Nusa Penida Holiday Planner

Aktuelle Flug-Deals nach Denpasar (DPS)

list_flight_deals
Read-onlyIdempotent

Aktuelle Flugangebote aus DACH-Städten nach Bali mit Filtern für Abflughafen, Preis, Reisezeitraum, Fluggesellschaft und Umsteigen.

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

Input Schema

NameRequiredDescriptionDefault
limitNoTrefferzahl (1-50, default 20).
offsetNoOffset für Pagination (0-500, default 0).
originNoIATA-Code oder Stadt (z.B. 'FRA', 'MUC', 'VIE', 'ZRH').
airlineNoAirline-Code, z.B. 'LH', 'EK', 'QR'.
sort_byNo
max_priceNo
min_priceNo
departure_toNoSpätester Abflug (YYYY-MM-DD).
max_transfersNoMaximale Anzahl Umstiege (0 = direkt).
departure_fromNoFrühester Abflug (YYYY-MM-DD).
max_duration_minutesNo

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 readOnly, idempotent and closed-world behavior, so the safety profile is covered. The description adds useful scope (results are limited to departures from DACH cities and to Bali as destination) but says nothing about pagination limits, default sorting, result size, or currency/price semantics, which matter for an 11-parameter listing tool.

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 well-formed sentence with no filler, front-loading the resource and following with the filter capabilities. Nothing is redundant, though the compressed list of filters could be structured more scannably.

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 11-parameter tool with no output schema and only 64% schema coverage, the description covers the core filtering intent but leaves result format, sorting behavior, pagination defaults and price units undisclosed. Adequate to get an agent started, insufficient to call it correctly in edge cases.

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 names five filter dimensions (departure airport, price, travel period, airline, transfers) that map onto origin, min/max_price, departure_from/to, airline and max_transfers. At 64% schema coverage this adds some orientation, but it omits sort_by, limit, offset and max_duration_minutes, so the description does not compensate for the uncovered parameters.

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 states a specific verb and resource ('Aktuelle Flugangebote' = current flight offers) plus origin scope (DACH cities) and destination (Bali), which clearly distinguishes it from the other list_* siblings covering activities, hotels, ferries, etc. Minor inconsistency: the title names Denpasar/DPS while the description only says 'Bali'.

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?

It enumerates available filter dimensions but gives no guidance on when to choose this tool versus siblings such as get_best_price or plan_trip, nor any exclusion or prerequisite. The agent must infer from the name alone that this is the browsing tool for flight offers.

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