Skip to main content
Glama
mafedelahoz

CuddlyNest Search & Listings MCP Server

by mafedelahoz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get CuddlyNest hotel rooms & prices

cuddlynest_listing_details
Read-only

Retrieve details for a specific CuddlyNest hotel: static listing info, live room options, prices, availability, and cancellation policies.

Instructions

Get details for a specific CuddlyNest hotel: static basics (name, location, description, amenities, images) from the listing page, plus room options, prices, availability and cancellation policies read from the public listing page rendered in a headless browser.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hotelYesCuddlyNest hotel URL or numeric product_id. The product_id is the trailing number in a listing URL, e.g. https://www.cuddlynest.com/hotel/us/le-meridien-boston-cambridge-4264955 -> 4264955.
roomsNoNumber of rooms (default: 1)
adultsNoNumber of adults (default: 2)
checkinNoCheck-in date (YYYY-MM-DD)
infantsNoNumber of infants (default: 0)
checkoutNoCheck-out date (YYYY-MM-DD)
childrenNoNumber of children (default: 0, or derived from childAges)
currencyNoISO 4217 currency code for prices (default: USD), e.g. USD, EUR, COP
childAgesNoAge of each child at check-in, e.g. [2, 7]. Sets `children` when given.
ignoreRobotsTextNoIgnore robots.txt for the listing-page fetch on this request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.1
    • removedInput schema / properties / destinationSlug
      Removed value: -{
-  "description": "CuddlyNest internal destination slug for the hotel's city (e.g. 'SantaMartaMagdalenaColombia'). Optional — derived from the listing page's city/state/country when omitted.",
-  "type": "string"
-}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The description goes beyond the readOnlyHint annotation by explaining that data is 'read from the public listing page rendered in a headless browser.' This usefully discloses the data source and the browser-rendering approach. It does not mention failure modes or latency, but it adds meaningful behavioral context on top of the 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?

The description is a single dense sentence with no filler. It front-loads the core purpose and packs the key output categories into a well-organized list, earning every word.

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?

With no output schema, the description does a good job listing the main return categories: static basics, room options, prices, availability, and cancellation policies. Combined with the fully documented input schema and readOnly/openWorld annotations, it is sufficient for an agent to select and invoke the tool correctly. Minor gaps such as exact response structure or error behavior are not critical here.

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 description coverage is 100%, so the input schema already documents all parameters clearly. The description adds high-level output context but no additional parameter-level semantics, so the baseline of 3 is appropriate.

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 clear verb and resource: 'Get details for a specific CuddlyNest hotel' and enumerates what is included (static basics, room options, prices, availability, cancellation policies). This makes it easy to distinguish from the sibling cuddlynest_search, which is about searching/discovering hotels rather than retrieving a specific listing.

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 phrase 'for a specific CuddlyNest hotel' clearly indicates this tool is for when the agent already has a hotel URL or product_id. It does not explicitly name cuddlynest_search as the alternative or state exclusions, but the contrast with the sibling tool is apparent and the usage context is clear.

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