Skip to main content
Glama

Deal details

get_deal
Read-onlyIdempotent

Everything about online deals by id (from search results): every option with its price, regular price, discount, nights, adults, children, board and the periods it can be used in; the description, notes and conditions (how and when the voucher is used), the address and map pin, images, extra discounts now, the voucher's validity, whether it has an online booking calendar, and the page url to buy it.

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": "get_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe deal's id.
idsNoUp to 5 deal ids at once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful context beyond that by disclosing the response contents (per-option pricing, voucher validity, 'extra discounts now', booking-calendar flag, buy URL), which matters because no output schema exists.

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?

One front-loaded sentence that opens with the core purpose and then enumerates payload fields; the list is long but every item carries information. Slight bloat from exhaustive field enumeration with no structural breaks.

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?

The rich field enumeration compensates for the absent output schema, which is good. However, with zero required parameters and both 'id' and 'ids' optional, the definition never explains the selection rule or the failure behavior for an unknown id, leaving a real gap for a detail-lookup tool.

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 both 'id' and 'ids' are already documented, giving a baseline of 3. The description says 'by id' but adds nothing about the batch array of up to 5 ids, the relationship between the two parameters, or what happens when both or neither are supplied despite zero required 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?

States a specific verb and resource ('Everything about online deals by id') and enumerates the concrete fields returned, so an agent knows exactly what this retrieves. It hints at provenance with '(from search results)' but never names a sibling tool such as search_deals explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical '(from search results)' suggests where the id comes from, but there is no statement of when to prefer this over search_deals or check_availability, and no guidance on batch vs single lookup. An agent must infer the routing.

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.