Skip to main content
Glama
Sign In

BookingKoala MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create booking

create_booking
Destructive

Start a new booking as a copy of an existing one: same customer, service and price. Copies the booking as Duplicate in its sidebar does. The copy is saved as a draft (list_drafts) with the same customer, address, service, extras and price; open form_url to pick the date and book it. Nobody is told until it is booked.

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": {
      "from_booking_id": "<from_booking_id>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
from_booking_idYesBooking to copy, from list_bookings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description adds substantial context beyond the annotations: the copy is saved as a draft, it inherits customer, address, service, extras and price, form_url is needed to finalize the booking, and nobody is notified until it is actually booked. This clarifies state and side effects for a creation workflow.

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?

The description is front-loaded and practical, but it repeats the copied fields in two places ('same customer, service and price' and then 'same customer, address, service, extras and price'), which adds slight 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 one-parameter create tool with annotations and no output schema, the description is complete: it explains the draft state, copied fields, next step via form_url, and notification behavior. An agent has enough information to invoke it correctly.

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 the single parameter is already well documented as the booking to copy from list_bookings. The description reinforces that it copies an existing booking but does not add new syntax or format details beyond the schema.

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 uses a specific verb and resource: it starts a new booking as a copy of an existing booking. It also distinguishes the operation from a normal direct booking by explaining that it mirrors the Duplicate sidebar action and creates a draft.

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 clearly states the use case: duplicating an existing booking and then opening form_url to pick a date and book it. However, it does not explicitly name alternatives such as reschedule_booking or explain when not to use this copy workflow.

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

All BookingKoala MCP Server and API by Cotlet 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