Skip to main content
Glama

Nexwin

by au.com.nexwin
OverviewDiscussionsAdmin

Cancel a booking

cancel_booking
Destructive

Cancels a booking (appointmentId from get_bookings) by PERMANENTLY DELETING it — it will not appear afterwards, even as canceled. Also removes its Zoom meeting and calendar event and emails the customer a cancellation. Cannot be undone. Before calling, tell the user which booking (customer, time) will be cancelled and that the customer will be emailed, and get their explicit yes; then pass confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYestrue only after the user has explicitly confirmed cancelling this specific booking in the conversation
appointmentIdYesFrom get_bookings

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
successNo
_environmentYesThe Nexwin country and environment that supplied the result
appointmentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "true only after the user has explicitly confirmed cancelling this specific booking in the conversation",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "appointmentId"
-]New value: +[
+  "appointmentId",
+  "confirm"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes well beyond them: it discloses the deletion semantics (won't appear even as canceled), the side effects (Zoom meeting, calendar event removal, customer email), irreversibility, and the required user-confirmation flow. This is rich, non-redundant behavioral context.

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?

Front-loaded with the core action and its destructive nature, then side effects, then the preconditions. Every clause carries information the agent needs; nothing is padding.

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?

With an output schema present, return values need no explanation, and the description covers the mutation's consequences, irreversibility, side effects, and confirmation protocol. Nothing needed to call it safely is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning by tying confirm to an explicit user 'yes' about a specific booking and reiterating appointmentId's origin. It reinforces the schema rather than merely restating it.

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 (cancel a booking) and immediately clarifies the scope by defining it as PERMANENT DELETION rather than a status change — which is exactly the distinction that separates it from reschedule_booking among the siblings. An agent can select it unambiguously.

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 states when to use it, that it cannot be undone, where appointmentId comes from (get_bookings), and the exact conversational precondition plus the confirm: true gate before invoking. No conditions are left 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 toolsInspect
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