Skip to main content
Glama

Search deals

search_deals
Read-onlyIdempotent

Search every deal online now on Crno Jaje (crnojaje.hr, Croatia): vouchers for hotel stays and trips, wellness and spa, toplice (thermal spas), skiing, beauty treatments, health check-ups, restaurants, activities, courses, driving schools and products. All filters are optional and combine. Put Croatian words for the service in query ("wellness", "masaža", "skijanje", "jacuzzi", "romantični vikend", "zubar"); word forms are matched. Place, price, nights, persons, board and dates have their own fields; get exact category and place names from list_categories and list_places. Each result has the deal page url (where the customer buys), the price from, the regular price, the discount, the EXTRA discounts active now and the voucher's validity; get_deal gives every option and the conditions. Order: the site's own (best first), or with query the best match first.

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": "search_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.
extra_discount_onlyNoOnly deals with an EXTRA discount active now (newsletter, card or site-wide voucher).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds real behavior beyond that: Croatian word-form matching in query, the default site ordering versus best-match ordering with query, and the contents of each result (deal page url, price from, regular price, discount, active EXTRA discounts, voucher validity). It stops short of describing empty-result behavior or how paging works, which the offset schema only hints at.

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 purpose, then filtering guidance, then result contents, then ordering — a sensible order with no filler sentences. It is dense and somewhat packed into a single run-on block, and "All filters are optional and combine" partially duplicates the later field-ownership sentence.

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

Completeness4/5

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

For a 22-parameter search with no output schema, the description carries the important load: it explains what comes back per result and how ordering works, which compensates for the absent output schema. Remaining gaps are minor (empty results, paging mechanics, limit/offset interplay) and are largely covered by the parameter descriptions.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by telling the agent that query accepts Croatian inflected words and is matched by word form, that category and place values must come from the sibling list tools, and that location/price/party/date constraints should not be stuffed into query. That is genuine routing semantics beyond the field descriptions.

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 verb and resource ("Search every deal") on a named marketplace (Crno Jaje, crnojaje.hr, Croatia) and enumerates the deal types covered (hotels, spa, toplice, skiing, restaurants, courses, products). An agent can distinguish this general search from get_deal or list_extra_discount_deals without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes work between siblings: put Croatian service words in query, get exact category and place names from list_categories and list_places, and use get_deal for every option and the conditions. It also states that all filters are optional and combine, and that places, prices, nights, persons and dates belong in their own fields rather than in query.

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.