Skip to main content
Glama

verychic_search_offers

Read-onlyIdempotent

Search and filter the current VeryChic offers by destination, country, price, discount, stars, flights, theme, or proximity — with optional sorting.

    When to use: when you already know roughly what the user wants — a place, a country,
    a budget, a minimum discount or star rating, flights vs hotel-only, a theme (e.g.
    pool, spa, romantic, last_minute), or hotels near a point (near_lat/near_lng, with an
    optional radius_km). To inspect one specific offer in depth use
    `verychic_offer_details`. All filters are optional and combine with AND; call it with
    no filter to browse the full current catalogue in catalogue order.

    Behaviour: read-only and anonymous; rate-limited to about 1 request per second.
    Filtering is done client-side over the live catalogue: `destination` is a
    case-insensitive substring (matched on destination or name), `country` is an exact
    case-insensitive match, `max_price`/`min_discount`/`min_stars` are numeric bounds,
    `flights_included` toggles flight-bearing vs hotel-only, and `theme` matches a curated
    label decoded from the catalogue's thematics tags. Use `sort_by` to order results
    (`discount`, `price`, `rating`, `stars`, or `distance`). Prices are in EUR and text is
    in French; there is no pagination. Returns the first `limit` matches after filtering
    and sorting. "Current" means live offers at call time; the catalogue changes over time.

    Returns a list of offer objects (same `source` + `external_id` pair for use with
    `verychic_offer_details`). Each offer also carries `discount` (percent off, may be
    null), `stars` (1-5, may be null), `price_label` (human-readable price unit, e.g.
    "à partir de par pers. pour 3 nuits" vs "par chambre" — read this before comparing
    prices), `price_with_flights` (EUR, null when not applicable), `flights_included`
    (bool), `rating` (hotel grade, often null in the catalogue), and `themes` (curated
    theme labels decoded from the catalogue's thematics tags, e.g. ["pool", "luxury"]).
    An empty list means no offer matched the filters.

    Proximity search: pass `near_lat` and `near_lng` (decimal degrees, together) to
    compute each offer's `distance_km` from that point; add `radius_km` to keep only
    offers within that distance, and/or `sort_by="distance"` for nearest-first.
    `distance_km` is null when no center is given.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of matching offers to return (default 20), applied after filtering and sorting. No pagination.
themeNoKeep only offers matching this curated theme, decoded from the catalogue's thematics tags. One of: adults_only, city_break, cruise, island, last_minute, luxury, mountain, nature, pool, romantic, rooftop, spa, sun, villa. Omit to not filter by theme.
countryNoExact country name, case-insensitive, as spelled in the (French) catalogue, e.g. 'France', 'Italie', 'Grece'. Omit to not filter by country.
sort_byNoSort the results: 'discount' (biggest discount first), 'price' (cheapest first), 'rating' (best-rated first), 'stars' (most stars first), 'distance' (nearest first, requires near_lat/near_lng). Offers missing the sort value are placed last. Omit to keep catalogue order.
near_latNoLatitude of a search center for proximity search, in decimal degrees. Must be given together with near_lng. Omit for no geo search.
near_lngNoLongitude of a search center for proximity search, in decimal degrees. Must be given together with near_lat. Omit for no geo search.
max_priceNoInclusive upper bound on the offer price, in EUR. Offers with no price are excluded when this is set. Omit for no price cap.
min_starsNoKeep only offers with at least this hotel star rating (1-5), parsed from the offer name. Offers with no detectable rating are excluded. Omit to not filter by stars.
radius_kmNoKeep only offers within this many kilometers of the near_lat/near_lng center. Requires near_lat and near_lng. Omit for no radius.
destinationNoCase-insensitive substring matched against each offer's destination AND name (e.g. 'paris', 'maldives', 'crete'). Omit to not filter by destination.
min_discountNoKeep only offers whose discount percentage is at least this value (e.g. 40 for '40% off or more'). Offers with no discount are excluded. Omit for no discount filter.
flights_includedNoFilter on whether flights are part of the offer: true keeps flight-bearing offers, false keeps hotel-only offers. Omit to not filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds substantial context: read-only and anonymous access, rate limit (~1 req/s), client-side filtering over a live catalogue, no pagination, and that the catalogue changes over time. No contradictions with annotations.

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?

The description is well-structured with clear sections (When to use, Behaviour, Proximity search). It is front-loaded with the main purpose. However, it is somewhat verbose and repeats details already present in the schema (e.g., parameter types). Minor redundancy prevents a perfect score.

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

Completeness5/5

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

Given the tool has 12 optional parameters, proximity search, sorting, and an output schema exists, the description is thorough: it covers all filters, their combination (AND), return format (list with key fields), edge cases (null values, empty list), and notes like text in French. An output schema exists, so return values need not be detailed, but the description still provides useful insight.

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

Parameters5/5

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

Schema coverage is 100%, baseline 3. The description greatly enhances parameter meaning: explains case-insensitivity for destination/country, exact match for country, numeric bounds for price/discount/stars, interdependence of proximity parameters (near_lat/near_lng), and how sort_by interacts with missing values. This goes well beyond the schema 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?

The description clearly states the tool searches and filters VeryChic offers by multiple criteria, and distinguishes it from the sibling tool `verychic_offer_details` which is for inspecting specific offers. The verb 'search and filter' combined with resource 'VeryChic offers' is specific and unambiguous.

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?

The 'When to use' section explicitly advises using this tool when the user's rough intent is known (destination, budget, etc.) and directs to `verychic_offer_details` for deeper inspection of a single offer. It also notes that calling with no filters returns the full catalogue, providing clear usage context.

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.

TDQS

A4.7/5.0
Disambiguation5/5

The two tools have completely distinct purposes: one searches/filters offers, the other retrieves details for a specific offer. No overlap in functionality.

Naming Consistency5/5

Both tools follow a consistent 'verychic_verb_noun' pattern: 'verychic_search_offers' and 'verychic_offer_details'.

Tool Count3/5

With only 2 tools, the set is minimal but covers the core browsing workflow (search and details). However, it falls below the typical 3-15 tool range, which suggests a slightly under-scoped surface.

Completeness3/5

The tools provide search and detail retrieval, which is reasonable for a read-only hotel deals server. However, missing capabilities like comparing multiple offers or filtering by date range are notable gaps.