Skip to main content
Glama

Chalet-Montagne.com

by com.chalet-montagne

Rechercher une location de vacances à la montagne

search_rentals
Read-only

Recherche des locations de vacances à la montagne en France parmi des milliers d'annonces (chalets, appartements, studios) louées en direct par leurs propriétaires — sans commission de réservation. Sans dates, les prix renvoyés sont des tarifs à la semaine ; avec des dates, le prix est le total du séjour demandé. Les prix sont indicatifs, à confirmer par le propriétaire. Chaque résultat contient un « id » à réutiliser avec get_rental_details et check_availability_and_price, et un lien vers la page du site à proposer à l'utilisateur.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage de résultats (10 par page).
sortNoTri des résultats. Défaut : pertinence.
guestsNoNombre de voyageurs (capacité de couchage minimale).
localeNoLangue des libellés et des liens renvoyés.fr
date_endNoDate de départ (YYYY-MM-DD). Requise si date_start est fournie.
amenitiesNoÉquipements exigés (tous devront être présents).
budget_maxNoBudget maximum en euros pour le séjour (ou pour la semaine si pas de dates).
date_startNoDate d'arrivée (YYYY-MM-DD). Recommandé : les prix deviennent exacts et la disponibilité est prise en compte.
destinationNoStation, massif, département ou domaine skiable français, en texte libre. Ex : "Les Gets", "Haute-Savoie", "Portes du Soleil". En cas d'ambiguïté le serveur propose des choix. Omettre pour chercher dans toutes les destinations.
bedrooms_minNoNombre minimum de chambres.
pets_allowedNotrue = uniquement les locations acceptant les animaux.
flexible_daysNoTolérance en jours autour des dates (0 = dates strictes).
property_typesNoTypes d'hébergement souhaités.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate read-only and open-world. The description adds behavioral details about pricing (weekly vs total, indicative) and the structure of results (id, link). It does not contradict 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?

The description is concise, covering purpose, pricing, and result format in a few sentences. It is front-loaded with the main action. Could be slightly more structured but is efficient.

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?

Given the 13 parameters and no output schema, the description explains the essential behavior (pricing, result contents) and links to sibling tools. It does not cover all parameters, but the schema does. Adequate for the complexity.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds context about date-related pricing behavior, but does not provide additional detail on individual parameters beyond what the schema already offers.

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 description clearly states the tool searches for mountain vacation rentals in France, listing property types (chalets, apartments, studios) and mentioning it's direct from owners with no booking fee. It distinguishes from siblings by noting that results contain an 'id' for use with get_rental_details and check_availability_and_price.

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 provides context on when to use the tool (searching for rentals) and explains pricing behavior with and without dates, implying that for detailed info the other tools should be used. However, it does not explicitly state when not to use this tool or compare directly with siblings.

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

All Chalet-Montagne.com 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: search, view details, check availability/price, and send inquiry. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores, e.g., search_rentals, get_rental_details, check_availability_and_price, send_rental_inquiry.

Tool Count5/5

4 tools is well-scoped for a rental assistant, covering search, details, availability/price check, and inquiry initiation without being too few or too many.

Completeness4/5

Covers the main workflow of finding and contacting owners; lacks tools for managing user inquiries or post-inquiry actions, but fits the direct-rental model without booking.

Resources