Skip to main content
Glama
Sign In

ekkor

by com.spocont
OverviewDiscussionsAdmin

booboooking_cancel

DestructiveIdempotent

Cancel a reservation on booboooking.com. Requires the reservation_id AND pin that were returned from the original booboooking_book call — both are needed as proof of booking ownership. The pin is also in the customer's confirmation email; a wrong pin is refused.

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": "<provider>",
      "reservation_id": "<reservation_id>",
      "pin": "<pin>"
    },
    "name": "booboooking_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
pinYesThe PIN returned from the original booking
providerYesProvider identifier (same as the one used for booking)
reservation_idYesThe `id` returned from the original booking (24-hex MongoDB ObjectId)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare the operation destructive, non-read-only, and idempotent. The description adds meaningful behavioral context by explaining the ownership proof requirement and that a wrong pin is refused.

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 compact and front-loaded with the action, followed by the required credentials and the refusal behavior. Every sentence adds useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive cancellation tool with full schema coverage and annotations, the definition covers the core action, credentials, source, and one important failure mode. It could mention the provider parameter or cancellation effects more explicitly, but the essential invocation context is present.

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 schema already documents all three parameters. The description goes beyond that by explaining why both reservation_id and pin are required together as proof of ownership and by noting that the pin also appears in the confirmation email.

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 states a specific verb and resource: cancel a reservation on booboooking.com. It clearly distinguishes this action from booking and retrieval siblings by identifying the original book call as the source of the credentials.

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?

The description makes the use case clear and specifies that the reservation_id and pin must come from the original booboooking_book call. It does not explicitly name alternatives such as get_booking for viewing details before cancellation, but the context is strong.

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

All ekkor 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