Skip to main content
Glama
Sign In
@striderlabs/mcp-ihg

@striderlabs/mcp-ihg

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ihg_get_hotel_details

Retrieve comprehensive details for a specific IHG hotel: amenities, policies, contact info, and photos.

Instructions

Get detailed information about a specific IHG hotel including amenities, policies, contact info, and photos.

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": {
      "hotel_id": "<hotel_id>"
    },
    "name": "ihg_get_hotel_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
hotel_idYesThe IHG hotel code (e.g. 'NYCDO', 'LAXCA')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Get' implies a read-only operation, and the listed content (amenities, policies, contact info, photos) indicates return value. Missing behavioral details include whether authentication is required, error handling, or any response format caveats.

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?

A single, focused sentence that immediately states the tool's purpose and key content areas. No wasted words or redundant technical details.

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?

For a simple single-parameter detail lookup, the description is adequate but leaves gaps: no mention of authentication despite a login sibling, no output schema to clarify structure, and no guidance on valid hotel_id formats beyond the schema example.

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% and the hotel_id parameter is already described with an example. The description adds little beyond 'specific hotel', so it does not significantly enhance parameter understanding beyond the schema.

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 retrieves detailed information for a specific IHG hotel, listing concrete categories (amenities, policies, contact info, photos). This distinguishes it from siblings like ihg_search_hotels and ihg_get_room_rates.

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 context is implied: the user must already have a specific hotel_id and wants comprehensive details. However, there is no explicit guidance on prerequisites (e.g., login via ihg_login) or differentiation from alternatives like ihg_get_room_rates.

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

Deploy Server

Other Tools