@striderlabs/mcp-ihg

ihg_get_reservation_details

Retrieve full IHG reservation details by entering your confirmation number. View booking information and manage your stay.

Instructions

Get full details for a specific IHG reservation by confirmation number.

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": {
      "confirmation_number": "<confirmation_number>"
    },
    "name": "ihg_get_reservation_details"
  }
}

Input Schema

Name	Required	Description	Default
`confirmation_number`	Yes	IHG confirmation number (e.g. '12345678')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Get full details' is vague and does not disclose expected response format, required authentication (especially with a sibling ihg_login), or any potential errors. It is a read operation, but the lack of behavioral detail such as pagination, authorization, or return fields makes this weak.

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 a single, clear sentence that achieves its purpose without unnecessary words. It is front-loaded and to the point.

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

Completeness2/5

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

With no output schema and no annotations, the description should compensate by explaining what 'full details' means, potential prerequisites (e.g., login), and how this tool differs from listing or modifying reservations. It does not, making it incomplete for a tool that likely returns a complex reservation object.

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?

The input schema has 100% description coverage, including an example. The tool description adds minimal extra value beyond 'confirmation number' being the key parameter. Baseline 3 is appropriate because the schema carries the explanatory load.

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's function: retrieving full details for a specific reservation using a confirmation number. It uses a specific verb ('Get') and resource ('IHG reservation'), and distinguishes itself from the sibling 'ihg_get_reservations' (likely list) by focusing on a single reservation.

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 when to use this tool: when you have a confirmation number and need full details for a single reservation, versus listing all reservations. It does not explicitly name alternatives or exclusions, but the 'by confirmation number' phrase provides clear context.

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

Deploy Server