Skip to main content
Glama

create_event

Schedule calendar events by specifying details like subject, start/end times, location, and attendees. Integrates with Microsoft Outlook via MCP server for efficient event management.

Instructions

Create a calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
attendeesNo
bodyNo
endYes
locationNo
startYes
subjectYes
timezoneNoUTC

Implementation Reference

  • The handler function for the 'create_event' tool. It constructs a calendar event payload from input parameters and uses graph.request to POST it to the Microsoft Graph API endpoint '/me/events' to create the event.
    @mcp.tool
    def create_event(
        account_id: str,
        subject: str,
        start: str,
        end: str,
        location: str | None = None,
        body: str | None = None,
        attendees: str | list[str] | None = None,
        timezone: str = "UTC",
    ) -> dict[str, Any]:
        """Create a calendar event"""
        event = {
            "subject": subject,
            "start": {"dateTime": start, "timeZone": timezone},
            "end": {"dateTime": end, "timeZone": timezone},
        }
    
        if location:
            event["location"] = {"displayName": location}
    
        if body:
            event["body"] = {"contentType": "Text", "content": body}
    
        if attendees:
            attendees_list = [attendees] if isinstance(attendees, str) else attendees
            event["attendees"] = [
                {"emailAddress": {"address": a}, "type": "required"} for a in attendees_list
            ]
    
        result = graph.request("POST", "/me/events", account_id, json=event)
        if not result:
            raise ValueError("Failed to create event")
        return result
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Create a calendar event' implies a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether it sends invitations, error conditions, rate limits, or what happens on success/failure. It mentions nothing about the calendar system or event lifecycle.

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 extremely concise ('Create a calendar event')—just three words. It's front-loaded with the core action and resource. There's no wasted text, though this conciseness comes at the cost of completeness.

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?

Given the complexity (8 parameters, mutation tool), lack of annotations, and no output schema, the description is incomplete. It doesn't provide enough context for an agent to understand how to use the tool effectively, what to expect, or handle edge cases. It's minimal for a tool with this parameter count and mutation nature.

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 description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'account_id', 'attendees', 'body', etc., mean, their formats, or relationships. With 8 parameters (4 required), this leaves significant gaps in understanding how to invoke the tool correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a calendar event' clearly states the action (create) and resource (calendar event), but it's somewhat vague about what constitutes a calendar event versus other event types. It distinguishes from siblings like 'create_contact' or 'create_email_draft' by specifying the resource type, but doesn't clarify how it differs from 'create_event' if there were multiple event types.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like authentication), when to use it instead of 'update_event' or 'respond_event', or any constraints. The agent must infer usage from the tool name alone.

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

Related 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/elyxlz/microsoft-mcp'

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