Caly

Decline booking

decline_booking

Destructive

Decline a booking request and notify the attendee, optionally with a reason. Ask the user — never choose for them. The reason is emailed to the attendee. Two steps: the first call returns CONFIRMATION_REQUIRED with a confirmToken; tell the user what will happen, then call again with the SAME arguments plus confirmToken.

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": {
      "bookingUid": "<bookingUid>"
    },
    "name": "decline_booking"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Shown to the attendee.
`bookingUid`	Yes	Booking UID (a string like '2NtaeaVcKfpmSZ4CthFdfk'), as returned by list_bookings or create_booking.
`confirmToken`	No	Leave empty on the first call. Then pass the token from the CONFIRMATION_REQUIRED answer.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that the attendee is notified by email, that the reason is emailed, and that the operation requires a two-step confirmation with a confirmToken. This gives the agent meaningful behavioral context for a destructive, non-idempotent action.

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?

The description is front-loaded with purpose and side effect, then gives the confirmation workflow in three tight sentences. Every sentence carries operational value with 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?

For a destructive two-step mutation with no output schema, the description covers the essential agent-facing concerns: user consent, notification side effect, and the confirmToken workflow. It is complete enough to prevent incorrect invocation.

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 useful meaning: the reason is emailed to the attendee and the second call must use the SAME arguments plus confirmToken. That clarifies parameter behavior beyond the schema text.

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 states a specific verb and resource: "Decline a booking request" and adds the side effect of notifying the attendee. It is clear what the tool does, but it does not explicitly distinguish the operation from siblings such as cancel_booking or confirm_booking.

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?

It provides a clear usage rule: "Ask the user — never choose for them" and explains the required two-step confirmation workflow. It does not, however, state when to prefer decline_booking over alternatives like cancel_booking or request_reschedule.

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

All Caly 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?