Skip to main content
Glama
Sign In
marriott_mcp

marriott_mcp

by YHRen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

modify_reservation

Preview reservation changes, then apply them with a confirmation token after explicit user approval; any altered parameter requires a new preview.

Instructions

Preview reservation changes. After explicit user approval, repeat identical parameters with confirmationToken. Changed parameters require a new preview.

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": {
      "confirmationNumber": "<confirmationNumber>"
    },
    "name": "modify_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
newCheckInNo
newCheckOutNo
newRoomTypeNo
specialRequestsNo
confirmationTokenNo
confirmationNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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. It discloses that this is a preview step and that confirmation is required, but it does not explicitly state whether the preview itself modifies the reservation or what side effects occur. It also lacks details on error handling or permission requirements.

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 two sentences, front-loaded with the core purpose and followed by the confirmation workflow. There is no redundant or filler content; every sentence adds value.

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?

The tool has 6 parameters, no output schema, and no annotations. The description explains the workflow but does not cover parameter semantics, expected output of the preview, or error conditions. An agent would struggle to construct valid calls or interpret results without additional context.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the parameters. It only mentions confirmationToken and the concept of repeating identical parameters, but does not describe the meaning or usage of newCheckIn, newCheckOut, newRoomType, or specialRequests. This is a significant gap for an agent to call the tool correctly.

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 states a specific verb ('Preview') and a clear resource ('reservation changes'), distinguishing it from sibling tools like cancel_reservation or get_reservation. It also conveys the two-phase nature of the operation without ambiguity.

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 explains the workflow: preview first, then confirm with a token, and that changed parameters require a new preview. It provides clear context on when to call the tool and the confirmation step, though it does not explicitly list alternative tools or exclusions.

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