Nexwin

Reschedule a booking

reschedule_booking

Destructive

Moves an existing booking (appointmentId from get_bookings) to a new time and emails the customer about the change. Before calling, tell the user which booking (customer, current time) is moving to which new time, and get their explicit yes; then pass confirm: true. Executes as soon as it is called with confirm: true.

Input Schema

TableJSON Schema

Name	Required	Description
`confirm`	Yes	true only after the user has explicitly confirmed this specific change in the conversation
`endTime`	Yes	ISO 8601 with UTC offset, e.g. 2026-09-20T15:00:00+10:00
`timezone`	No	IANA timezone; defaults to the booking’s existing timezone
`startTime`	Yes	ISO 8601 with UTC offset, e.g. 2026-09-20T14:00:00+10:00
`appointmentId`	Yes	From get_bookings

Output Schema

TableJSON Schema

Name	Required	Description
`message`	No
`success`	No
`_environment`	Yes	The Nexwin country and environment that supplied the result
`appointmentId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "true only after the user has explicitly confirmed this specific change in the conversation",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "appointmentId",
-  "startTime",
-  "endTime"
-]New value: +[
+  "appointmentId",
+  "startTime",
+  "endTime",
+  "confirm"
+]

First observedSep 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructive/non-idempotent, but the description adds genuinely new behavioral context: the customer is emailed, and the operation executes immediately once confirm: true is passed. That execution-timing and side-effect disclosure goes well beyond the structured fields.

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 tight sentences, front-loading what the tool does before the confirmation protocol and the immediate-execution warning. No filler.

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

Completeness5/5

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

An output schema exists so return values need no explanation, and the description covers the safety-critical confirmation flow and side effect. Nothing an agent needs in order to call this correctly is missing.

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 all five parameters (including ISO 8601 formats, timezone default, and the confirm gate) are already documented in the schema. The description only restates the confirm requirement and appointmentId origin, adding little beyond the structured data. 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 verb and resource ('Moves an existing booking ... to a new time') plus a side effect (emails the customer). This clearly distinguishes it from siblings cancel_booking and create_booking without needing to open either schema.

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 prescribes the pre-call workflow: tell the user which booking (customer, current time) is moving where, get an explicit yes, then pass confirm: true. It also names the prerequisite source for appointmentId (get_bookings), leaving nothing to inference.

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

All Nexwin tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?