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

@striderlabs/mcp-ihg

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ihg_login

Log in to your IHG One Rewards account to authenticate and enable hotel search, booking, and reservation management tools.

Instructions

Log in to your IHG One Rewards account. Required before using most other tools. Maintains a browser session for subsequent calls.

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": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "ihg_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesYour IHG account email address
passwordYesYour IHG account password

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so the description must disclose behavior. It mentions the browser session persistence, which is a key trait. However, it doesn't disclose failure modes, authentication errors, or idempotency, so it's useful 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?

Two concise sentences, front-loaded with the action, no filler.

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?

For a simple 2-param login tool, the description covers purpose, prerequisite status, and session behavior. Given no annotations or output schema, it's reasonably complete, though could mention what happens on failure.

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?

Input schema has descriptions for both parameters (email and password) with 100% coverage. The tool description adds no extra param semantics 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?

Clearly states it logs into an IHG One Rewards account, using a specific verb and resource. It also notes it's required before most other tools, distinguishing it as a prerequisite among the sibling tools.

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?

Explicitly says 'Required before using most other tools' and 'Maintains a browser session for subsequent calls,' giving clear when-to-use context. It doesn't mention exceptions or alternatives, but for a login tool that's sufficient.

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