mcp-meetsync

rescheduleBooking

Move a confirmed meeting to a new future time. Provide new start and end times; conflict detection runs automatically for all participants. Only bookings with confirmed status can be rescheduled.

Instructions

Use this tool when you need to move a confirmed meeting to a new time. The new startTime must be in the future. Conflict detection runs automatically for all participants. Only bookings with status "confirmed" can be rescheduled.

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": {
      "bookingId": "<bookingId>",
      "startTime": "<startTime>",
      "endTime": "<endTime>"
    },
    "name": "rescheduleBooking"
  }
}

Input Schema

Name	Required	Description
`bookingId`	Yes	UUID of the booking to reschedule.
`startTime`	Yes	New start time as ISO 8601 datetime with timezone offset. Must be in the future.
`endTime`	Yes	New end time as ISO 8601 datetime with timezone offset.
`reason`	No	Optional reason for the reschedule.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Apr 24, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions conflict detection and status validation but omits important details like whether notifications are sent, if the previous slot is freed, or permission requirements. It provides some transparency but not comprehensive.

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?

Four concise sentences, each adding essential information. The purpose is front-loaded, and every sentence earns its place without redundancy or verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers key constraints but lacks any mention of what the tool returns (e.g., success indication, updated booking object) or error conditions. Given no output schema, this is a gap in completeness.

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 the description adds limited value beyond restating constraints. It mentions 'conflict detection' and 'only confirmed' status, which are not in the schema, but does not elaborate on the 'reason' parameter or output behavior.

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 ('move'), resource ('a confirmed meeting'), and specific constraints (new time, only confirmed bookings). It distinguishes from siblings like 'cancelBooking' and 'updateParticipant' by focusing on rescheduling.

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 explicitly states when to use the tool ('when you need to move a confirmed meeting') and includes conditions (future start time, conflict detection, confirmed status). However, it does not mention explicit alternatives, which would raise it to a 5.

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