Skip to main content
Glama

Create booking

create_booking

Ask the user — never choose for them. The attendee's name, email, time zone, the event type and the start time come from the user. Book a meeting on one of the caller's event types for an attendee. Sends the usual confirmation emails and calendar invites. Get a free start time from find_available_slots first; required booking questions come from get_event_type's bookingFields.

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": {
      "eventTypeId": "<eventTypeId>",
      "start": "<start>",
      "attendee": "<attendee>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesStart time in ISO 8601, in UTC (e.g. '2026-10-01T09:00:00Z'). Pick it from find_available_slots so it is actually free.
guestsNoExtra guest emails to invite.
attendeeYesAsk the user — never choose for them. The person being booked.
metadataNoFree-form string key/values stored on the booking (at most 50 keys).
eventTypeIdYesNumeric event type ID, as returned by list_event_types.
lengthInMinutesNoMeeting length, only for event types that offer several lengths. Defaults to the event type's length.
bookingFieldsResponsesNoAnswers to the event type's custom booking questions, keyed by booking field slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / attendee / description
      Previous value: -"The person being booked."New value: +"Ask the user — never choose for them. The person being booked."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower; the description still earns credit by disclosing the side effects an agent can't infer: "Sends the usual confirmation emails and calendar invites." It omits what happens when the slot is taken or the call fails, which is the main remaining gap.

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?

Three tight sentences with no filler, each carrying a distinct instruction. The causal ordering is slightly off — the warning about asking the user precedes any statement of what the tool does — which costs a point on front-loading.

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?

Covers the purpose, prerequisites, side effects and data provenance for a 7-parameter write tool with nested attendee data and no output schema. What an agent would still want before calling blind — conflict/error behavior and what the response contains — is absent, but the annotations and required-field list cover most of the risk.

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 baseline is 3; the description adds provenance above the schema by specifying that name, email, time zone, event type and start time must come from the user, and that bookingFields responses come from get_event_type. That is real guidance the schema does not encode, though individual param meanings are left entirely to the schema.

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: "Book a meeting on one of the caller's event types for an attendee." That is clear enough to differentiate from generic siblings like create_calendar_event or create_connection_event, but it never explicitly names a boundary or contrast against those near-neighbors.

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

Usage Guidelines5/5

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

Explicit workflow prerequisites: "Get a free start time from find_available_slots first; required booking questions come from get_event_type's bookingFields." It names the alternative tools and the condition for using them, plus the strong directive "Ask the user — never choose for them" for attendee data.

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