Amadeus Hotel API MCP Server

amadeus_hotel_offer

Retrieve detailed information about a hotel offer by its ID. Access updated availability and pricing from a previous search.

Instructions

Get detailed information about a specific hotel offer using its ID. This provides comprehensive details about an offer that was found in a previous search result, including updated availability and pricing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "offerId": "<offerId>"
    },
    "name": "amadeus_hotel_offer"
  }
}

Input Schema

Name	Required	Description	Default
`offerId`	Yes	The unique identifier of the offer from a previous search

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description must fully convey behavior. It indicates this is a read operation (get details) but does not mention authentication requirements, rate limits, or what happens if the ID is invalid. The behavioral coverage is adequate but not comprehensive.

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?

The description is two sentences long, front-loading the primary action. Every sentence adds value, and there is no redundant or unnecessary information.

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?

Given the simplicity of the tool (one parameter, no output schema), the description adequately explains the purpose and returned content (updated availability and pricing). It could mention potential errors or missing IDs, but overall it is complete enough for a get-detail operation.

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 description coverage is 100% for the single parameter 'offerId', which already describes it as the unique identifier from a previous search. The tool description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 verb 'Get detailed information' and the resource 'specific hotel offer using its ID'. It also distinguishes the tool by mentioning it is for offers from a previous search result, differentiating it from sibling tools like search or list.

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?

The description implies usage after a previous search ('offer that was found in a previous search result'), providing clear context. However, it does not explicitly state when not to use this tool or name alternatives, leaving room for ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server