Skip to main content
Glama

verychic_offer_details

Read-onlyIdempotent

Get full details plus per-date availability and prices for one specific VeryChic offer.

    When to use: after `verychic_search_offers` returned an offer you want to inspect —
    pass that offer's `source` and `external_id` here. You must obtain those two
    identifiers from a search result first; this tool does not search.

    Behaviour: read-only and anonymous; rate-limited to about 1 request per second;
    prices in EUR, text in French. Availability is looked up for roughly the next 5
    months. For tour-operator packages (`source` = 'ORCHESTRA_TO') VeryChic exposes no
    date-availability endpoint: `availabilities` is then empty and
    `availabilities_supported` is false — meaning "not supported", NOT "sold out".

    Returns an object with: `offer` (same fields as a search result, plus `offer_url`),
    `advantages`, `included_added_values`, `non_included_added_values`, `gallery`
    (image URLs), `availabilities` (one entry per check-in date with `date`, `price`,
    `currency`, `nights`, `days`, `departure_city_code`), `availabilities_supported`
    (bool), and `cheapest_price` (lowest available price, or null when none).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesThe offer's source type, copied verbatim from the `source` field of a `verychic_search_offers` result. One of 'ORCHESTRA' (a single hotel) or 'ORCHESTRA_TO' (a tour-operator package). Packages have no per-date availability.
external_idYesThe offer's numeric `external_id`, copied from a `verychic_search_offers` result. Identifies the offer together with `source`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
offerYes
galleryYes
advantagesYes
availabilitiesYes
cheapest_priceYes
included_added_valuesYes
availabilities_supportedYes
non_included_added_valuesYes

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare read-only and non-destructive, and description adds rate limit (1 req/s), currency (EUR), language (French), availability window (~5 months), and special behavior for tour-operator packages (availabilities empty but meaning not supported, not sold out). This adds value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with sections: summary, when to use, behavior, returns. It is concise (about 150 words) and front-loaded with the purpose. Every sentence is informative.

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?

Despite the output schema not being shown, the description fully documents the return structure. It covers all relevant details including edge case for tour operators. The tool has only 2 simple parameters, and the description addresses all contextual needs.

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%, but description adds context: explains that source can be 'ORCHESTRA' or 'ORCHESTRA_TO' and that tour-operator packages have no per-date availability. This enriches the parameter meaning.

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 gets full details plus per-date availability for one specific VeryChic offer. It distinguishes from the sibling 'verychic_search_offers' by specifying that identifiers must come from a search result.

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 states when to use (after search returns an offer) and when not to (does not search). Provides clear prerequisite: must obtain source and external_id from search result first.

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.