Skip to main content
Glama

Complete booking

complete_booking
Destructive

Mark a confirmed booking as completed.

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": "complete_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoAn ISO 8601 date and time.
latitudeNo
longitudeNo
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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the description should add what that means in practice: whether completion is reversible, whether the client is notified, whether related records change, or what permissions are required. The single sentence adds nothing beyond restating the title, leaving the destructive flag unexplained.

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?

A single short sentence with the state precondition front-loaded and no filler. It is efficient, though the terseness is a symptom of missing content rather than of disciplined editing.

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

Completeness2/5

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

For a destructive, open-world mutation with five parameters, partial schema coverage and no output schema, one sentence is inadequate. The agent lacks reversibility, side-effect, permission and optional-parameter guidance needed to call it safely.

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 coverage is only 40% across five parameters, and the description explains none of them. The optional at, latitude and longitude fields (plausibly completion time and location) are undocumented in both places, so the agent cannot know whether to supply them or what effect they have.

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?

"Mark a confirmed booking as completed" names a specific verb (mark as completed) and resource (booking), and the word "confirmed" implies the state transition is only valid from a confirmed state. It does not explicitly contrast with siblings like cancel_booking or reject_booking, so it falls short of a 5.

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 prerequisite that the booking be already confirmed is implied guidance, but there is no explicit when-to-use/when-not-to-use statement and no named alternative (e.g., use cancel_booking to void instead). The agent must infer the selection rule from context.

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