Skip to main content
Glama

Reject booking

reject_booking
Destructive

Reject a booking and refund any payment the client already made. This cannot be undone.

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": {
      "booking_id": "<booking_id>"
    },
    "name": "reject_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds the substantive behavioral fact that a payment refund is triggered and the action is irreversible. It stops short of saying what happens if the refund fails or what the response contains.

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?

Two short sentences, zero filler, with the irreversible warning front-loaded right after the action. Every clause earns its place.

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

Completeness3/5

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

Covers the essential risk profile for a destructive mutation, but for a tool that moves money it omits failure modes (e.g., refund errors, partial refunds) and gives no hint of the result shape with no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: business_id is documented with a pointer to list_businesses, but booking_id carries no description at all. The description contributes nothing about either parameter, leaving the required booking_id identifier undocumented in prose.

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?

States a specific verb and resource (reject a booking) plus a key side effect (refund of client payment), which goes beyond the name alone. However, it never distinguishes itself from the close sibling cancel_booking, so an agent cannot tell from the description which decline path applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The scenario is implied – decline a booking and return the client's money – but there is no explicit when-to-use, when-not-to-use, or pointer to cancel_booking as the alternative. The agent must infer the boundary between rejecting and cancelling.

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