ski-france.com Agent Search

Search ski apartments

search_apartments

Read-onlyIdempotent

Main apartment-level search for winter ski accommodation in French ski areas and ski resorts. Results are apartments, not whole accommodations. Put destination, ski area, ski resort or accommodation names into keywords. Use structured parameters for amenities, rooms, living space, slope distance, ski area size, parent areas, accommodation category, chalet type, pets and price sorting. Put the traveller count into partySize, not keywords. Use weekId and durationWeeks for one- or two-week price, availability, bookability and special-discount data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Result page, starting at 1.
`pets`	No	Pet policy.
`areas`	No	Parent-area values from get_search_options.
`weekId`	No	Fixed weekly winter arrival date id from get_search_options. Required for week-specific price, availability, bookabilityStatus and special-discount comparison.
`entityId`	No	Optional precise search-scope entity id from resolve_search_keywords. Use together with entityType.
`keywords`	No	Natural-language destination or accommodation keywords, for example a ski resort, ski area, accommodation name or free text. Use the structured filter parameters for amenities and property requirements.
`amenities`	No	Amenity values from get_search_options.
`partySize`	No	Traveller count. Results are restricted to apartments whose capacity is at least this party size within the matching website occupancy bucket.
`priceSort`	No	Result sorting. Status remains the primary order, followed by price and party-size category.	default
`entityType`	No	Optional precise search-scope entity type from resolve_search_keywords. Use together with entityId to restrict results to a resolved parent region, ski area, ski resort, district or accommodation.
`minBedrooms`	No	Minimum number of bedrooms. Value 8 means 8 or more.
`minBathrooms`	No	Minimum number of bathrooms. Value 8 means 8 or more.
`skiAreaSizes`	No	Ski-area size categories from get_search_options.
`durationWeeks`	No	Stay duration in weeks. Two weeks requires weekId.
`minSquareMeters`	No	Minimum living space in square metres.
`accommodationType`	No	Optional accommodation type.
`accommodationCategories`	No	Premium and luxury accommodation categories from get_search_options.
`maxDistanceToSlopeMeters`	No	Maximum distance to piste, lift or gondola in metres.

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context: results are apartments only, and weekId/durationWeeks are needed for week-specific data like price and bookability. This is beyond annotation data, though it does not detail response format or pagination.

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 dense but efficiently structured: three sentences cover purpose, scope, and key parameter guidance. Each sentence adds unique information. It is slightly long given the number of parameters, but remains focused and front-loaded.

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?

For an 18-parameter search tool with no output schema, the description covers essential usage patterns and distinguishes from sibling searches. However, it does not explain the response structure or pagination behavior, which would be helpful given no output schema. Overall, it is sufficiently complete for a complex tool.

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 all 18 parameters already have descriptions. The description adds value by clarifying usage patterns (e.g., 'Put the traveller count into partySize, not keywords') and grouping parameters by intent. It enriches the schema but does not fully compensate for the absence of an output schema.

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 it is the 'Main apartment-level search for winter ski accommodation in French ski areas and ski resorts.' It specifies the resource (apartments), the verb (search), and explicitly distinguishes from whole accommodations, which differentiates it from sibling tools like list_accommodations.

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?

Provides clear guidance on how to use parameters: put destinations in keywords, use structured filters for amenities/property requirements, put party size in partySize, and use weekId/durationWeeks for price/availability data. It implies when to use this search (for apartment-level results) but does not explicitly name alternative tools or list exclusion criteria.

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

All ski-france.com Agent Search tools Inspect

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 clearly distinct purpose: separate tools for different entity details (accommodation, ski area, resort), distinct search vs. list operations, and specialized tools for ski pass prices and search vocabulary. No overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_accommodation_detail, list_ski_areas, search_apartments). Verbs are appropriately chosen (get, list, search, resolve), and there are no mixed conventions.

Tool Count5/5

With 10 tools covering destination discovery, accommodation details, apartment search, pricing, and search utilities, the count is well-scoped for a ski accommodation search domain. No unnecessary tools or missing essentials.

Completeness5/5

The tool set covers the full user journey: vocabulary setup (get_search_options), keyword resolution (resolve_search_keywords), destination lists (list_ski_areas/resorts), accommodation lists (list_accommodations), detailed info (get_*_detail), apartment search with pricing (search_apartments), and ski pass pricing (get_ski_pass_prices). No obvious gaps for an information/query-focused server.

Resources

Need Help?