@mnicole-dev/calcom-mcp-server

get-booking

Need a specific booking? Provide its booking UID to retrieve the booking details directly.

Instructions

Get a specific booking by its UID.

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": {
      "bookingUid": "<bookingUid>"
    },
    "name": "get-booking"
  }
}

Input Schema

Name	Required	Description	Default
`bookingUid`	Yes	The booking UID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It clearly indicates a read/retrieval operation and identifies the uniqueness key, but it does not disclose return format, not-found behavior, or authorization requirements.

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?

A single, front-loaded sentence with no filler; every word carries meaning and the description is immediately scannable.

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?

The tool is simple: one required parameter and no nested objects or enums. The description conveys what is retrieved and how to identify it, which is sufficient for basic invocation. The absence of an output schema leaves the exact response shape undocumented, but the description indicates the result is a booking.

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 description coverage is 100% – bookingUid is already described as 'The booking UID'. The description's 'by its UID' only reinforces that and adds no new semantic detail 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?

Uses a specific verb and resource: 'Get a specific booking by its UID.' The selection key UID is stated, and the resource 'booking' clearly distinguishes it from sibling tools like get-schedule, list-bookings, and booking mutations.

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 phrase 'specific booking by its UID' implies it is meant for single-item retrieval when the UID is already known, contrasting with list-bookings for collections. However, there is no explicit when-to-use or when-not-to-use guidance, and no sibling alternatives are named.

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