Skip to main content
Glama

Deals with an extra discount now

list_extra_discount_deals
Read-onlyIdempotent

Deals with an EXTRA discount active right now, on top of the deal's own price: a newsletter discount, a card discount (Mastercard, Diners, ZABA) or a site-wide voucher, worded as the deal page words them (extra_discounts), with a count of each kind (extra_discount_kinds). Tell the customer about them: they make the deal cheaper today. Same filters as search_deals; biggest discount first by default.

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

Input Schema

NameRequiredDescriptionDefault
nearNoWith a town in place: deals around it too (up to 40 km).
sortNobest (default; the site's order, or the best match with query), price_asc, price_desc, discount_desc, newest.
boardNoThe lowest board accepted: breakfast also takes half board and more.
limitNoHow many deals (default 10).
placeNoA town, island, region or country: "Opatija", "Krk", "Istra", "Dalmacija", "Zagorje", "Slovenija", "Hrvatska", or "Inozemstvo" for any country abroad.
queryNoCroatian words for the service, venue or theme ("wellness", "hotel s bazenom", "masaža lica", "Hotel Eden"). Leave places, prices, nights, persons and dates to their own fields.
venueNoA hotel, restaurant, salon or partner by name ("Hotel Eden", "Terme Tuhelj").
abroadNotrue: only deals abroad; false: only deals in Croatia.
adultsNoStays: an option for at least this many adults.
nightsNoStays: exactly this many nights.
offsetNoSkip this many (paging: next_offset of the previous call).
date_toNoYYYY-MM-DD: the last day (stays: departure). The voucher's validity and the option's periods must fit.
seasideNoOnly deals on the Croatian coast (Istra, Kvarner, Dalmacija).
categoryNoA category name from list_categories ("Wellness i spa", "Toplice").
childrenNoStays: an option for at least this many children with the adults.
date_fromNoYYYY-MM-DD: the first day the customer wants to use the voucher (stays: arrival).
price_maxNoEUR: an option (one voucher) costs at most this.
price_minNoEUR: an option costs at least this.
nights_maxNoStays: at most this many nights.
nights_minNoStays: at least this many nights.
pet_friendlyNoOnly deals known to accept pets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description adds real behavioral context beyond that — that deals are worded as the deal page words them, that counts per kind are returned, and that default ordering is biggest discount first. It stops short of describing paging behavior or what an empty result means.

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?

Front-loaded with the defining constraint, then the discount types, then the return fields, then filters and default ordering. Dense but each clause carries information; the parenthetical field names are slightly technical for a customer-facing instruction but earn 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?

With 21 optional parameters and no output schema, the description does well to name the two returned fields and the default sort, but it leaves paging (offset/limit) and any result-shape detail unaddressed. Adequate for the tool's complexity but not fully self-sufficient.

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 100%, so all 21 parameters are self-documenting; the description adds only the efficient shorthand that the filter set matches search_deals and that 'biggest discount first' is the default sort. That is a useful gloss on the sort default, but nothing beyond the schema for the remaining filters.

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

Purpose5/5

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

States a specific resource (deals with an extra discount active right now, layered on the deal's own price) and enumerates the kinds: newsletter, card (Mastercard, Diners, ZABA), and site-wide voucher. It also names the returned fields (extra_discounts, extra_discount_kinds), which separates it cleanly from search_deals without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Says explicitly to use it to tell the customer about these discounts because 'they make the deal cheaper today', and points to search_deals as the shared filter model. It does not say when NOT to use it versus search_deals, but the selection condition is clear enough to choose correctly.

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.