Roraima holiday rentals

Search holiday rentals

search_listings

Read-onlyIdempotent

Search Roraima listings by town or province, country, dates and number of guests. With check_in and check_out, only listings free on those nights are returned, each with its total price and a link to its page with dates and guests filled in. The amenity filters return only nights listings whose host has stated that amenity. accommodation_type tells whether one booking takes the whole place (private) or one place per guest in a shared room such as a dormitory (shared, priced per person).

Input Schema

Name	Required	Description
`limit`	No	Most results to return. Default 10.
`guests`	No	Number of guests.
`country`	No	ISO 3166-1 alpha-2 country code, e.g. IT.
`parking`	No	true: only listings with parking, free or paid (get_listing says which).
`check_in`	No	Arrival date, YYYY-MM-DD.
`language`	No	Language of names, descriptions and page links. Default en.
`location`	No	Town name, or the two-letter code of an Italian province (SS for the province of Sassari). Province names are matched only as town names.
`check_out`	No	Departure date, YYYY-MM-DD.
`entire_place`	No	true: only listings where the guest has the entire place, not a room.
`pets_allowed`	No	true: only listings that accept pets, also on request (get_listing says which).
`air_conditioning`	No	true: only listings with air conditioning.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 7, 2026

addedInput schema / properties / air_conditioning

Added value: +{
+  "description": "true: only listings with air conditioning.",
+  "type": "boolean"
+}

addedInput schema / properties / entire_place

Added value: +{
+  "description": "true: only listings where the guest has the entire place, not a room.",
+  "type": "boolean"
+}

addedInput schema / properties / parking

Added value: +{
+  "description": "true: only listings with parking, free or paid (get_listing says which).",
+  "type": "boolean"
+}

addedInput schema / properties / pets_allowed

Added value: +{
+  "description": "true: only listings that accept pets, also on request (get_listing says which).",
+  "type": "boolean"
+}

Changed1 schema field changedOct 4, 2026

changedInput schema / properties / location / description

Previous value: -"Town name or Italian province code, e.g. Valledoria or SS."New value: +"Town name, or the two-letter code of an Italian province (SS for the province of Sassari). Province names are matched only as town names."

First observedOct 3, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description adds substantial context: check_in/check_out returns only listings free on those nights with total price and a pre-filled page link, and amenity filters return only listings whose host has stated the amenity. This is valuable behavioral detail beyond 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose and then behavioral details. The third sentence about accommodation_type is not represented in the schema and may confuse, but otherwise the description is efficient and well-structured.

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 optional parameters, no output schema, and annotations covering the safety profile, the description supplies useful return-content and filter-semantics details. It omits pagination/limit behavior and does not route to sibling tools for follow-up, but the schema already documents parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the combined check_in/check_out behavior and the 'host has stated that amenity' nuance for amenity filters. It also mentions accommodation_type, which is not in the schema and may be an output field, but the added filter semantics justify a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb 'Search' and resource 'Roraima listings' with scope by town/province, country, dates and guests. It does not name sibling tools such as get_listing or search_products to distinguish when to use this versus them, so sibling differentiation is absent.

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 gives clear context for searching listings with location, date and guest filters, implying discovery use. However, it never explicitly says when to use this tool instead of get_listing for details or search_products, and offers no exclusions or alternatives. Usage is therefore implied rather than stated.

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

All Roraima holiday rentals tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?