Skip to main content
Glama

arcasos-rentals

by com.arcasos

get_rental_details

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
NameRequiredDescriptionDefault
check_inNoOptional move-in date (YYYY-MM-DD). Must be provided together with check_out. Enables period quote + date availability. Future dates only.
check_outNoOptional 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_idYesRental UUID or slug from search results. Both formats supported.

TDQS

A4.8/5.0
Behavior5/5

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

Discloses return content (full Schema.org Accommodation), eligibility filter, quote-only behavior, deposit/breakdown details, and clarifies the agent never initiates payment. No annotations provided, so description carries the full burden and does so thoroughly.

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?

Description is detailed and every sentence contributes useful information. Front-loaded with core purpose. Slightly verbose but appropriate given the tool's optional quote behavior and safety note.

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, so description explains return value (full Schema.org Accommodation) and optional quote behavior comprehensively. Also covers eligibility and payment safety, making the context complete for an agent.

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 covers parameter format/requirements (100% coverage). Description adds behavioral nuance: quote-only estimate, discount applied, total + breakdown, deposit shown separately, and that dates must be together. This goes beyond the schema, though rental_id is not significantly enhanced.

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?

Clear verb+resource+method: 'Get detailed information for a specific rental by ID or slug.' Distinguishes from siblings by specifying it's for details on a specific result after search.

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 states when to use: 'Use after search_rentals_natural or search_rentals_structured when user wants details on a specific result.' Also outlines eligibility constraints (approved + available + bookable).

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

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

A4.4/5.0
Disambiguation5/5

Each tool has a distinct purpose: two search variants are clearly separated by query type, and get_rental_details is for post-search detail retrieval. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: search_rentals_natural, search_rentals_structured, get_rental_details. The naming is uniform and predictable.

Tool Count5/5

Three tools is a well-scoped set for a rental search and details server. Each tool serves a necessary function without redundancy or bloat.

Completeness5/5

The surface covers the full agent workflow: search (natural and structured) and retrieve details. Booking is intentionally outside the agent's scope, so there are no missing operations for the stated purpose.

Resources