arcasos-rentals

get_rental_details

Read-only

Get detailed information for a specific rental by ID or slug. Returns full Schema.org Accommodation including pricing, amenities, location, photos. Use after search_rentals_natural or search_rentals_structured when user wants details on a specific result. Only returns publicly-eligible rentals (approved + available + bookable). Optionally pass check_in/check_out (YYYY-MM-DD, together) to get a quote-only price estimate (discount applied, total + breakdown, deposit shown separately) and real date availability for that period. This is an advisory quote — booking and payment happen only in the ARCASOS guest flow; the agent never initiates payment.

Input Schema

TableJSON Schema

Name	Required	Description
`check_in`	No	Optional move-in date (YYYY-MM-DD). Must be provided together with check_out. Enables period quote + date availability. Future dates only.
`check_out`	No	Optional move-out date (YYYY-MM-DD). Must be provided together with check_in, and be after check_in. The check_out day is not occupied (next check-in allowed).
`rental_id`	Yes	Rental UUID or slug from search results. Both formats supported.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJun 25, 2026

addedInput schema / properties / check_in

Added value: +{
+  "description": "Optional move-in date (YYYY-MM-DD). Must be provided together with check_out. Enables period quote + date availability. Future dates only.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / check_out

Added value: +{
+  "description": "Optional move-out date (YYYY-MM-DD). Must be provided together with check_in, and be after check_in. The check_out day is not occupied (next check-in allowed).",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

First observedMay 20, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the description is not carrying the safety burden. It adds real behavioral context anyway: only publicly-eligible rentals are returned (approved + available + bookable), date arguments produce an advisory quote-only price with discount, breakdown and separate deposit, and payment is explicitly out of scope.

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?

Front-loaded with purpose and routing before the optional-date behavior, and each sentence carries distinct information. It is denser than strictly necessary, with the quote mechanics packed into one long sentence, but nothing is filler.

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?

No output schema exists, yet the description summarizes the return shape (Schema.org Accommodation with pricing, amenities, location, photos) and the quote breakdown. For a three-parameter read tool with annotations already covering safety, nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3 and the schema already documents the mutual dependency of check_in/check_out and the ID/slug formats. The description still adds value by explaining the effect of supplying the dates (quote-only estimate plus real date availability), which is beyond the schema's field-level text.

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?

States a specific verb and resource ('Get detailed information for a specific rental by ID or slug') and names the return payload (full Schema.org Accommodation). It also distinguishes itself from the sibling search tools by explicitly positioning itself as the follow-up detail call.

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?

Directly states when to use it: 'after search_rentals_natural or search_rentals_structured when user wants details on a specific result.' It also draws a hard boundary around adjacent actions by noting booking and payment only happen in the ARCASOS guest flow and the agent never initiates payment.

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

All arcasos-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?