marriott_mcp

Overview Schema Source Related Servers Discussions Admin

redeem_points

Preview and book a specific award offer after receiving explicit user approval, using the provided confirmation token.

Instructions

Preview and book an exact award offer from a usePoints search. Only after explicit user approval pass confirmationToken. Never retry an unknown submission outcome.

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

Input Schema

Name	Required	Description	Default
`email`	No
`phone`	No
`rooms`	No
`adults`	No
`checkIn`	No
`hotelId`	No
`offerId`	No
`checkOut`	No
`children`	No
`lastName`	No
`roomCode`	No
`firstName`	No
`specialRequests`	No
`confirmationToken`	No
`governmentEligibilityConfirmed`	No
`specialRateEligibilityConfirmed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the need for user approval before confirmation and warns against retrying unknown outcomes. However, it does not describe the mutation's side effects, such as points deduction or reservation creation details, leaving significant behavioral unknowns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loading the core purpose and then critical usage rules. It is concise and well-structured, with no fluff. However, the brevity sacrifices completeness, which is penalized elsewhere.

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

Completeness1/5

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

Given the tool has 16 parameters, no schema descriptions, no output schema, and no annotations, the description is severely incomplete. It does not explain how preview and booking differ, what parameters are required for each scenario, or what the response contains. This is inadequate for an agent to call the tool correctly.

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

Parameters1/5

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

The schema has 0% description coverage, and the description provides no parameter explanations beyond mentioning confirmationToken. With 16 parameters, none of which are self-explanatory from names alone (e.g., governmentEligibilityConfirmed, specialRateEligibilityConfirmed), this is a critical gap. The description fails to compensate for the missing schema documentation.

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: preview and book an exact award offer from a usePoints search. It distinguishes itself from siblings like search_hotels and get_room_options by specifying the redemption context. The verb 'redeem' is implicit in the name but the description clarifies the specific action.

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?

It provides explicit conditions: only pass confirmationToken after explicit user approval, and never retry an unknown submission outcome. It implies the tool should be used after a usePoints search, giving context. However, it does not name alternative tools or explicitly state when not to use it, leaving some ambiguity.

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

Deploy Server