Skip to main content
Glama

Cancel a booking

dosai_cancel_booking
Destructive

Mark a booking as cancelled by its external_id: its pending reminders are withdrawn, the record stays in history. Works ONLY for bookings that came from the owner's own system (created with dosai_upsert_booking, they have an external_id in dosai_list_bookings). A booking the bot made through Google Calendar, Altegio, YCLIENTS or iiko is cancelled there, by the owner or by the bot's own cancel function. It does not write to the client and does not touch the calendar event. Requires editor role.

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": {
      "project_id": "<project_id>",
      "external_id": "<external_id>"
    },
    "name": "dosai_cancel_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
external_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real context beyond them: pending reminders are withdrawn, the record is preserved in history, the client is not written to, the calendar event is untouched, and editor role is required. These are exactly the side-effect and permission facts an agent needs before invoking a destructive tool.

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?

Front-loads the action, then scope, then side-effects, then permissions — a sensible order with no filler. The mid-paragraph sentence enumerating external systems and alternatives is long and dense, which costs a bit of scannability.

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 two-parameter destructive tool with no output schema, the definition covers scope, side effects, prerequisites (editor role), and the alternative route for externally sourced bookings. Nothing an agent needs in order to call it correctly 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 50% and external_id has no schema description, but the prose explains that it identifies a booking created by the owner's system and can be found via dosai_list_bookings, giving it meaning beyond a 1-200 character string. project_id is only covered by the schema reference to dosai_list_projects, so coverage is not fully compensated.

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 ('Mark a booking as cancelled by its external_id') plus the immediate consequence ('record stays in history'), which is enough for an agent to distinguish it from sibling cancel tools such as dosai_cancel_invite or dosai_cancel_scheduled_message without opening any 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?

Gives an explicit positive precondition ('Works ONLY for bookings that came from the owner's own system ... created with dosai_upsert_booking') and an explicit exclusion with the correct alternative path ('A booking the bot made through Google Calendar, Altegio, YCLIENTS or iiko is cancelled there'). Both the when and the when-not are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources