Skip to main content
Glama

Airsockfly

Request date change

request_date_change

Ask to move the dates of a hotel, tour or car rental booking. Creates a change request that the provider handles.

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": {
      "vertical": "<vertical>",
      "bookingId": "<bookingId>",
      "newStartDate": "<newStartDate>",
      "newEndDate": "<newEndDate>"
    },
    "name": "request_date_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional note for the service provider.
verticalYesService type.
bookingIdYesIdentifier of one booking inside an order, from get_booking.
newEndDateYesNew end date, YYYY-MM-DD.
newStartDateYesNew start date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the mutability profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description is not carrying that burden. It still adds real value by clarifying that this only files a change request that the provider processes, signalling that the outcome is not immediate and may be rejected — context the annotations do not convey.

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?

Two short sentences with no filler; the action and the crucial 'request, not confirmation' nuance are both front-loaded. Nothing could be removed without losing meaning.

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?

With full schema coverage, no output schema, and annotations covering the safety profile, the definition gives an agent enough to call it correctly. The one gap is what the returned change request looks like or how approval is tracked, which is minor given the absence of an output schema.

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 description coverage is 100%, so every parameter (including the bookingId source 'from get_booking' and date formats) is already documented in the schema. The description's mention of hotel/tour/car loosely mirrors the vertical enum but adds no new syntax or constraint detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a concrete verb ('move the dates') and names the resource and supported verticals (hotel, tour, car rental booking), which separates it from cancel_booking or create_booking without opening a schema. It stops short of naming any sibling explicitly, so it is clear but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Ask to move the dates...' implies the use case (an existing booking whose dates must change), but there is no explicit when-not guidance and no routing to alternatives such as cancel_booking for bookings that cannot be moved. Usage is inferable but not spelled out.

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