Skip to main content
Glama
Sign In
@aiwerk/mcp-server-cal

@aiwerk/mcp-server-cal

Official
by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

cal_create_booking

Create a new booking by providing event type ID, start time (ISO 8601), attendee name, email, and timezone. Optionally include notes, guest emails, or metadata.

Instructions

Create a new booking. Required: eventTypeId, start (ISO 8601), attendeeName, attendeeEmail, attendeeTimezone. Optional: notes, guests (array of emails), metadata.

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>",
      "attendeeName": "<attendeeName>",
      "attendeeEmail": "<attendeeEmail>",
      "attendeeTimezone": "<attendeeTimezone>"
    },
    "name": "cal_create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventTypeIdYes
startYes
attendeeNameYes
attendeeEmailYes
attendeeTimezoneYes
notesNo
guestsNo
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose side effects, authentication requirements, rate limits, or failure conditions (e.g., conflicts). It only states it creates a booking, leaving behavioral traits unclear.

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?

Single sentence listing required and optional parameters, front-loaded with the action. No redundant information, but could benefit from slight restructuring for readability.

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?

No output schema, and the description does not describe return values or side effects. For a creation tool, this is incomplete; agents need to know what is returned (e.g., booking ID) and whether confirmation occurs.

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 0%, and the description merely lists parameter names without explaining their purpose or adding context beyond the schema. For instance, 'metadata' is an object but no clarification on expected keys or usage.

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?

Description starts with 'Create a new booking', uses a specific verb and resource. It lists required and optional fields, clearly distinguishing it from sibling tools like cancel, reschedule, etc.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs siblings. The description only states what the tool does, not when to prefer it over alternatives like cal_reschedule_booking or cal_cancel_booking.

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

Deploy Server

Other Tools