Skip to main content
Glama

get_alternative_dates

Read-onlyIdempotent

Des séjours de même durée, proches des dates demandées, et réellement disponibles. Utile quand create_booking_session ne trouve rien : sur seize chambres, deux jours de décalage suffisent souvent. Rend jusqu’à trois propositions, de la plus proche à la plus lointaine, avec leur prix tout compris.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_alternative_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
adultsNoNombre d’adultes. 2 par défaut.
end_dateYesDépart souhaité, AAAA-MM-JJ.
start_dateYesArrivée souhaitée, AAAA-MM-JJ.
property_idNoL’hôtel : « corniche » (Best Western Plus La Corniche) ou « voiles » (Hôtel-Rooftop Les Voiles), ou son identifiant (`list_properties`). Absent = Hôtel-Rooftop Les Voiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / property_id
      Added value: +{
      +  "description": "L’hôtel : « corniche » (Best Western Plus La Corniche) ou « voiles » (Hôtel-Rooftop Les Voiles), ou son identifiant (`list_properties`). Absent = Hôtel-Rooftop Les Voiles.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior. The description adds real value beyond them: at most three proposals, ordered from nearest to farthest, each with all-inclusive pricing, and the days-offset search logic. Lacks only a note on how far it searches or whether it is per-property scoped outside the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short sentences: what it returns, when to use it with a rationale, and the shape of the result. Front-loaded and zero filler.

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?

There is no output schema, so the description correctly describes the return (up to three ranked proposals with prices). Combined with a fully documented input schema this is close to complete; only search-window limits and cross-property behavior are unstated.

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?

Schema coverage is 100%, so every parameter is already documented including the property_id aliases and defaults. The description's phrase 'même durée' implies start/end are treated as a duration pair but adds no syntax or constraint detail beyond the schema. Baseline 3 applies.

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 outcome — same-duration stays near the requested dates that are actually available — and names the sibling tool it complements (create_booking_session). Nothing about it could be confused with get_rooftop_availability or get_stay.

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?

Gives an explicit trigger ('quand create_booking_session ne trouve rien') and justifies it with a concrete rationale about delta days on sixteen rooms. The agent knows exactly when to reach for this instead of the booking tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources