Skip to main content
Glama

registry

by global.rootz.rental

rental_search

Search vacation rental properties in the Caribbean. YOU ARE THE BUYER'S AGENT — search on behalf of your human. After searching, create a session (rental_session_create) and add your best picks (rental_session_add). Share the bridge URL with your human.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree text search across name, description, region
limitNoResults per page (default 20, max 50)
islandNoIsland name: Grand Cayman, Cayman Brac, Little Cayman, St. Lucia
regionNoRegion: Seven Mile Beach, North Side, Rum Point, West Bay, Soufriere, Rodney Bay, etc.
sleepsNoMinimum guests the property sleeps
amenityNoRequired amenity: pool, beach_access, ocean_view, wifi, kitchen, ac, parking
countryNoCountry code: KY (Cayman Islands) or LC (St. Lucia)
bedroomsNoMinimum bedrooms
max_priceNoMaximum nightly rate in USD
min_priceNoMinimum nightly rate in USD
property_typeNo

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided. Description identifies it as a search operation (read-only) but does not disclose any behavioral traits like rate limits, caching, or response format. Minimal added value beyond purpose.

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 plus workflow instruction. Every sentence adds value: purpose, role, follow-up actions. No redundancy.

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 11 parameters, no output schema, and no annotations, the description covers the essential usage flow. Missing details about output structure or special behavior, but the workflow guidance compensates.

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 high (91%), so the schema already documents parameters well. Description adds no extra meaning or usage hints for individual parameters.

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?

Description clearly states 'Search vacation rental properties in the Caribbean' with specific verb and resource. Distinct from siblings like rental_property (single property) and rental_availability (availability check).

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

Usage Guidelines5/5

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

Explicitly instructs the agent to act as buyer's agent, search, then create session and add picks, sharing bridge URL. Provides clear workflow context and distinguishes from subsequent steps.

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

All registry toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

Most tools target distinct actions, but the presence of both 'search' and 'rental_search' could cause confusion, and 'fetch' overlaps slightly with 'rental_property'. However, descriptions clarify the differences.

Naming Consistency3/5

While most tools use a 'rental_' prefix, two tools ('fetch', 'search') lack it, and the naming style varies between verb-noun and noun-only (e.g., 'rental_availability' vs 'rental_search'). This inconsistency could confuse an agent.

Tool Count5/5

With 16 tools, the set covers a comprehensive range for a Caribbean rental assistant, including search, property details, pricing, availability, licensing, market intelligence, and session management. Each tool serves a clear purpose.

Completeness4/5

The tool set covers the core lifecycle (search, view details, create sessions, add picks), but lacks session update/delete functionality. Also, 'fetch' and 'search' seem redundant with rental-focused tools. Overall, the domain is well-covered for an agent workflow.

Resources