Skip to main content
Glama
mafedelahoz

CuddlyNest Search & Listings MCP Server

by mafedelahoz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search CuddlyNest hotels

cuddlynest_search
Read-only

Search CuddlyNest by destination to get top hotel matches with ratings, images, distance, and amenities. Use the returned product IDs to retrieve live rooms, prices, and availability.

Instructions

Search CuddlyNest for a destination and the top hotels there. Returns place candidates (city/region + coordinates + total property count) and a list of hotels — name, listing URL, star + guest rating, and (when available) images, distance from the centre and key amenities. Pass a hotel's product_id from the results to cuddlynest_listing_details for live rooms and prices. The hotel list is top-matches scale (~10-60), not the full inventory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
hotelsOnlyNoReturn only the hotel list, skipping place candidates (default false).
destinationYesDestination to search (city / area), e.g. 'Santa Marta, Colombia'.
fullCityListNoAlso pull the broader city hotel list (~60) from the geo-page API when it can be resolved — a couple of extra requests. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • addedInput schema / properties / fullCityList
      Added value: +{
+  "description": "Also pull the broader city hotel list (~60) from the geo-page API when it can be resolved — a couple of extra requests. Default true.",
+  "type": "boolean"
+}
    • addedInput schema / properties / hotelsOnly
      Added value: +{
+  "description": "Return only the hotel list, skipping place candidates (default false).",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark this as read-only and open-world, and the description adds useful behavioral context: it returns a limited top-matches list rather than the full inventory, includes fields only 'when available', and can return place candidates. This goes beyond what annotations declare without contradicting them.

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?

Four concise sentences, each adding distinct value: purpose, return payload, next-step routing, and scale caveat. There is no redundant or filler text.

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

Completeness5/5

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

Despite having 11 parameters and no output schema, the description gives enough on selection and invocation: what the search returns, the shape of hotel entries, the limited scale, and how to proceed to listing details. The parameter details are handled by the fully covered schema, so nothing critical is missing.

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 schema already documents all 11 parameters. The description adds no new parameter-level meaning; it only explains the overall result shape. This matches the baseline for well-covered schemas.

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 opening sentence names the action and resource ('Search CuddlyNest for a destination and the top hotels there') and the return types are specified (place candidates, hotel list). It also names the sibling tool in the handoff ('Pass a hotel's product_id ... to cuddlynest_listing_details'), so an agent can distinguish search from details.

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 makes it clear this tool is the entry-point search and that live rooms/prices are obtained via cuddlynest_listing_details, which is an explicit alternative routing. It also sets expectations that the list is top-matches (~10-60) and not full inventory, but it doesn't state explicit 'do not use when...' conditions beyond that.

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