Skip to main content
Glama
84emllc
by 84emllc

schedule_event

Schedule a meeting by creating an invitee for a Calendly event type at a specified start time, with invitee details, timezone, location, and optional guests or custom questions.

Instructions

Schedule a meeting by creating an invitee for a specific event type and time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_typeYesURI of the event type to schedule
start_timeYesStart time for the event (ISO 8601 UTC format, e.g., 2025-10-02T18:30:00Z)
utm_mediumNoUTM tracking parameter for medium
utm_sourceNoUTM tracking parameter for source
event_guestsNoArray of additional email addresses to include (max 10)
invitee_nameNoFull name of the invitee (alternative to first_name/last_name)
utm_campaignNoUTM tracking parameter for campaign
invitee_emailYesEmail address of the invitee
invitee_phoneNoPhone number for SMS reminders (E.164 format, e.g., +14155551234)
location_kindNoType of meeting location (e.g., zoom_conference, google_conference, physical, ask_invitee)
invitee_timezoneYesTimezone of the invitee (e.g., America/New_York)
location_detailsNoLocation details (required for physical meetings or custom locations)
invitee_last_nameNoLast name of the invitee
invitee_first_nameNoFirst name of the invitee
questions_and_answersNoArray of question and answer pairs for booking form
Behavior2/5

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

With no annotations, the burden falls on the description to disclose side effects, but it only says 'creating an invitee'. It does not explain that this mutates external calendars, sends invitations, or has cancellation implications. The write nature is implied but not elaborated.

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?

The description is a single, front-loaded sentence with zero filler. Every word contributes to the core purpose, making it highly concise and efficiently structured.

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?

This tool has 15 parameters, no output schema, and no annotations, yet the description is only one sentence. It fails to mention return value (e.g., booking confirmation/URL), behavior on scheduling conflicts, or required parameter combinations. This is inadequate for the tool's complexity.

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%, so the schema fully documents all 15 parameters. The description adds minimal extra value by highlighting event type and time, but doesn't clarify optional groupings or dependencies (e.g., invitee_name vs first/last name, physical location details). Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description states the primary action ('Schedule a meeting') and the resource created ('an invitee') for a specific event type and time. This clearly distinguishes it from sibling tools like list_events or cancel_event. However, it omits other required inputs like invitee_email and timezone, so it's not fully precise.

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 guidance is provided on when to use this tool versus alternatives such as get_event_type_availability or list_event_types. It does not mention prerequisites like OAuth authentication or checking availability before scheduling. The usage context is entirely absent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/84emllc/calendly-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server