Skip to main content
Glama
Sign In
AIOProductOS

AIOProductOS

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Remote

Reschedule Booking

reschedule_booking
Idempotent

Reschedule an existing booking by providing its ID and a new ISO 8601 start time; the system updates the booking and notifies the invitee.

Instructions

Reschedule a booking to a new start time (ISO 8601) and return the result — the invitee is notified. A write. Resolve booking_id via list_bookings first. booking_id and start are required.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start": "2026-07-20T15:00:00Z",
      "booking_id": "book_7"
    },
    "name": "reschedule_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesNew start time, ISO 8601 (e.g. 2026-07-20T15:00:00Z) (required).
booking_idYesBooking id to move, from list_bookings (required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.14
  2. Removedv0.1.12
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false (write) and idempotentHint=true (idempotent). The description adds that it notifies the invitee, providing valuable behavioral context beyond annotations. No contradictions.

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 sentences: first states purpose and effect, second gives prerequisite and requirement. Front-loaded, no fluff.

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?

Covers purpose, parameters, prerequisite, and side effect (notification). Without output schema, describing the return result would improve completeness, but current level is sufficient for agent use.

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 has 100% coverage with clear descriptions. Description adds context: booking_id comes from list_bookings, and start is ISO 8601. This supplements the schema meaningfully.

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 verb 'Reschedule' and resource 'booking', specifies the new start time format (ISO 8601), and notes that the invitee is notified. It distinguishes itself from sibling tools like 'cancel_booking' and 'list_bookings'.

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 instructs to resolve booking_id via list_bookings first, preventing misuse. It also notes that both booking_id and start are required, guiding correct invocation.

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

Deploy Server

Other Tools