Skip to main content
Glama

Aurinia — book across venues via your AI assistant

cancel

Idempotent

Cancels a booking at a network venue. Takes provider_id and item={booking_id}, where booking_id comes from list_current_bookings. A cancellation is reversible — the freed slot or bed can be booked again — which is why this tool is not marked destructive. If the user is not yet authorized at that venue the call returns a consent link instead. Authorization: one Telegram consent per venue, which also covers later calls.

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": {
      "provider_id": "<provider_id>",
      "item": "<item>"
    },
    "name": "cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesWhat to cancel: {booking_id:'<id from list_current_bookings>'}.
provider_idYesVenue id as returned by find_providers (e.g. rudko-vertebrolog).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / item / description
      Added value: +"What to cancel: {booking_id:'<id from list_current_bookings>'}."
    • addedInput schema / properties / provider_id / description
      Added value: +"Venue id as returned by find_providers (e.g. rudko-vertebrolog)."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

The description adds real value beyond the annotations by explaining why destructiveHint=false: the cancellation is reversible because the freed slot or bed can be booked again. It also discloses that an unauthorized venue returns a consent link rather than cancelling, and that one Telegram consent per venue covers later calls. However, it does not address the idempotentHint=true behavior, so an agent cannot tell from the description whether repeating a cancellation is safe or errors.

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?

Purpose and argument shape are front-loaded, and each sentence carries information about behavior or authorization. The closing authorization sentence partially overlaps the preceding consent-link sentence, so there is some redundancy.

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 mutation tool with no output schema, the definition covers what an agent needs: the cancellation semantics, the precondition for booking_id, reversibility, and the alternate consent-link outcome when the venue is not yet authorized.

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 both provider_id (with an example venue id) and item are fully documented in the schema. The description restates the item={booking_id} shape and the booking_id provenance, both of which the schema already says, so it adds little new parameter meaning over the structured fields.

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?

Opens with a specific verb and resource ('Cancels a booking at a network venue') and pins down the exact argument shape, item={booking_id}. That is enough for an agent to separate it from book, reschedule, and list_current_bookings 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes the precondition clearly by naming list_current_bookings as the source of booking_id, so an agent knows the required prior step. It never explicitly names an alternative for the adjacent intent (e.g. reschedule), so it stops short of full when/when-not routing.

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