@striderlabs/mcp-marriott

get_reservation

Retrieve your Marriott reservations by providing a confirmation number or view all upcoming bookings.

Instructions

Retrieve existing Marriott reservation details. Requires being logged in. Returns upcoming reservations or a specific booking by confirmation number.

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

Input Schema

Name	Required	Description	Default
`confirmationNumber`	No	Optional confirmation number to retrieve a specific reservation. Omit to get all upcoming reservations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Without annotations, the description carries the burden. It states 'Requires being logged in' and implies read-only behavior by saying 'Retrieve' and 'Returns upcoming reservations'. This is sufficient for a simple retrieval tool, though an explicit read-only hint would be ideal.

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 sentences, no filler, front-loaded with purpose. Every sentence provides essential information.

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 tool's simplicity (one optional param, no output schema), the description is complete: it states the action, prerequisites, and the two result types. It does not explain return values, but retrieval tools are generally self-explanatory.

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?

Schema coverage is 100% with a description for the only parameter. The description adds context beyond the schema: 'Omit to get all upcoming reservations' clarifies the dual behavior. This adds value beyond the basic schema description.

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 'Retrieve existing Marriott reservation details', specifying the resource (reservation) and action (retrieve). It distinguishes from siblings like cancel_reservation, modify_reservation, etc., which are mutation 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?

The description includes a prerequisite ('Requires being logged in') and explains the two modes: retrieve all upcoming reservations or a specific one by confirmation number. However, it does not explicitly tell when to avoid using this tool compared to alternatives like get_stay_history or status.

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

Deploy Server