@striderlabs/mcp-marriott

search_hotels

Find Marriott hotels in any destination by providing dates. Returns details including name, brand, rating, location, and nightly rate.

Instructions

Search for Marriott hotels by destination and dates. Returns hotel names, brands, ratings, locations, and nightly rates.

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": {
      "destination": "<destination>",
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>"
    },
    "name": "search_hotels"
  }
}

Input Schema

Name	Required	Description
`rooms`	No	Number of rooms (default: 1)
`adults`	No	Number of adults per room (default: 1)
`checkIn`	Yes	Check-in date in YYYY-MM-DD format (e.g., '2025-07-01')
`checkOut`	Yes	Check-out date in YYYY-MM-DD format (e.g., '2025-07-07')
`children`	No	Number of children (default: 0)
`maxResults`	No	Maximum number of results to return (default: 10, max: 50)
`destination`	Yes	Destination city or area (e.g., 'New York, NY', 'Paris, France', 'Miami Beach')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A3.8/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 burden. It mentions returns fields (names, brands, ratings, locations, rates) but does not disclose ordering, pagination, authentication requirements, or limitations (e.g., only Marriott hotels). The description is adequate but lacks depth for a tool with no annotations.

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, front-loaded with verb and resource. Every sentence adds value: first defines action and input, second defines output. No redundant or missing words.

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 7 parameters, no output schema, no annotations, and 15 sibling tools, the description is fairly complete for a search tool. It specifies output fields and input scope. However, it lacks details on default ordering, error conditions, and integration with other tools (e.g., after search, select_room).

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 the schema already documents all 7 parameters. The description adds context by specifying that it returns hotel names, brands, ratings, etc., but does not add meaning to individual parameters beyond what the schema provides. The mention of 'Marriott hotels' adds slight value not in schema.

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 verb 'Search' and the resource 'Marriott hotels', with specific scope by destination and dates, and lists return fields (hotel names, brands, ratings, locations, nightly rates). It distinguishes from siblings like get_hotel_details or get_room_options, which are more specific.

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

Usage Guidelines3/5

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

The description implies usage for initial search, but does not explicitly state when to use this tool vs alternatives like select_room or get_reservation. No exclusions or prerequisites are mentioned, which would help an agent choose correctly among 16 sibling tools.

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

Deploy Server