@striderlabs/mcp-marriott

check_in

Process mobile check-in for a Marriott reservation using the confirmation number. Optionally specify room preferences and arrival time to receive room number and mobile key.

Instructions

Complete mobile check-in for an upcoming Marriott reservation. May return room number and mobile key availability.

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

Input Schema

Name	Required	Description
`roomPreferences`	No	Room preferences (e.g., 'high floor, away from elevator')
`confirmationNumber`	Yes	Reservation confirmation number
`estimatedArrivalTime`	No	Estimated arrival time (e.g., '3:00 PM')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A3.5/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 cover behavioral traits. It hints at return values (room number, key availability) but does not discuss side effects, required authentication, or failure modes.

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 with no fluff. The key information is front-loaded.

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

Completeness3/5

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

Lacks output schema and annotations. While the description indicates return values, it does not cover error conditions or preconditions like login status or check-in window timing.

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?

Schema coverage is 100%, so parameters are already well-documented. The description adds a concrete example for 'roomPreferences', providing slight additional context.

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 specific action ('complete mobile check-in') and the resource ('upcoming Marriott reservation'). This distinguishes it from siblings like 'get_reservation' and 'select_room'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives such as 'select_room' or 'modify_reservation'. No prerequisites or conditions for use are mentioned.

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

Deploy Server