Odile Labs

Cancel a request booking

cancel_request

DestructiveIdempotent

Cancel the confirmed booking held on a request, removing it from the business calendar. It cannot be undone; only do it when the customer asked. Use this for a booking made under a request; for one made without a request, use send_to_business with the cancel_booking skill. Needs a live grant with scope read_cancel or book. Calling it again returns the same result. Returns cancelled, booking_id and when. Refused with outcome_uncertain when the calendar cannot confirm the booking (read get_request), and grant_required without access. Requires direct:tasks.

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": {
      "request_id": "<request_id>"
    },
    "name": "cancel_request"
  }
}

Input Schema

Name	Required	Description	Default
`request_id`	Yes	The request_id returned by open_request or shared by the assistant that opened it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / request_id / description

Added value: +"The request_id returned by open_request or shared by the assistant that opened it."

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag destructive and idempotent, and the description corroborates rather than contradicts them: 'It cannot be undone' and 'Calling it again returns the same result.' It goes further with the required scope (read_cancel or book), the direct:tasks requirement, the failure modes (outcome_uncertain, grant_required) and the return payload, none of which the annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the action and irreversibility before the routing and auth details, and nearly every clause carries needed information. It is dense but not padded, though the returns/error enumeration makes it longer than strictly necessary for a one-parameter tool.

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, idempotent, open-world mutation with no output schema, the description covers side effects, reversibility, authorization scopes, idempotency behavior, return values, and refusal modes. An agent has everything needed to decide and call correctly.

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% and the request_id schema entry already explains its provenance from open_request. The description mentions 'a request' but adds no format, validation, or edge-case meaning beyond the schema, so the 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?

The description names a specific verb and resource ('Cancel the confirmed booking held on a request') and its side effect ('removing it from the business calendar'). It is immediately distinguishable from siblings like get_request or send_to_business.

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?

It gives an explicit precondition ('only do it when the customer asked') and an explicit routing rule: this tool for a booking made under a request, send_to_business with the cancel_booking skill for one made without. It also names the fallback when the call is refused with outcome_uncertain (read get_request).

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

All Odile Labs 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?