@striderlabs/mcp-ihg

ihg_get_rewards_balance

Retrieve your IHG One Rewards points balance, tier status, and account summary. Get a clear snapshot of your rewards status.

Instructions

Get IHG One Rewards points balance, tier status, and account summary for the logged-in user.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

A4.2/5.0

Behavior3/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 of behavioral disclosure. It indicates a read operation ('Get') and defines the user scope, but does not explicitly state that no data is modified, whether authentication is required, or how errors are handled. It adds some context but falls short of full transparency.

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 sentence of 15 words, directly stating the action and the resource. It is front-loaded with 'Get' and contains no filler, making it efficient and well-structured.

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 (no parameters, no output schema), the description is quite complete: it states what is retrieved (balance, tier status, summary) and for whom (logged-in user). It could be more explicit about prerequisites or return format, but for this scope it is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing to explain. The description does not need to add parameter details, and with no schema properties, the description vocabulary is not needed to compensate. Baseline 4 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 tool retrieves IHG One Rewards points balance, tier status, and account summary for the logged-in user. It uses a specific verb 'Get' and names the exact resource, distinguishing it from sibling tools like ihg_get_rewards_history or ihg_get_hotel_details.

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 the tool is used to query the current user's rewards account by mentioning 'logged-in user', providing clear context. However, it does not explicitly state when to use this tool vs alternatives like ihg_get_rewards_history, nor does it mention exclusions. This is clear context but lacks explicit exclusions, so a 4 is appropriate.

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

Deploy Server