Skip to main content
Glama
merajmehrabi

Outlook Calendar MCP

by merajmehrabi

create_event

Create new calendar events or meetings in Microsoft Outlook by specifying subject, date, time, location, and optional details like attendees or calendar name. Manage events locally with privacy-focused processing.

Instructions

Create a new calendar event or meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attendeesNoSemicolon-separated list of attendee email addresses (optional)
bodyNoEvent description/body (optional)
calendarNoCalendar name (optional)
endDateNoEnd date in MM/DD/YYYY format (optional, defaults to start date)
endTimeNoEnd time in HH:MM AM/PM format (optional, defaults to 30 minutes after start time)
isMeetingNoWhether this is a meeting with attendees (optional, defaults to false)
locationNoEvent location (optional)
startDateYesStart date in MM/DD/YYYY format
startTimeYesStart time in HH:MM AM/PM format
subjectYesEvent subject/title

Implementation Reference

  • The handler function for the 'create_event' MCP tool. It calls the createEvent helper from scriptRunner.js, processes the result, and returns a formatted MCP response with success or error content.
      handler: async (eventDetails) => {
        try {
          const result = await createEvent(eventDetails);
          return {
            content: [
              {
                type: 'text',
                text: `Event created successfully with ID: ${result.eventId}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error creating event: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    },
  • The input schema for the 'create_event' tool, defining properties and requirements for event creation parameters.
    inputSchema: {
      type: 'object',
      properties: {
        subject: {
          type: 'string',
          description: 'Event subject/title'
        },
        startDate: {
          type: 'string',
          description: 'Start date in MM/DD/YYYY format'
        },
        startTime: {
          type: 'string',
          description: 'Start time in HH:MM AM/PM format'
        },
        endDate: {
          type: 'string',
          description: 'End date in MM/DD/YYYY format (optional, defaults to start date)'
        },
        endTime: {
          type: 'string',
          description: 'End time in HH:MM AM/PM format (optional, defaults to 30 minutes after start time)'
        },
        location: {
          type: 'string',
          description: 'Event location (optional)'
        },
        body: {
          type: 'string',
          description: 'Event description/body (optional)'
        },
        isMeeting: {
          type: 'boolean',
          description: 'Whether this is a meeting with attendees (optional, defaults to false)'
        },
        attendees: {
          type: 'string',
          description: 'Semicolon-separated list of attendee email addresses (optional)'
        },
        calendar: {
          type: 'string',
          description: 'Calendar name (optional)'
        }
      },
      required: ['subject', 'startDate', 'startTime']
    },
  • src/index.js:34-35 (registration)
    Registers the Outlook tools, including 'create_event', by calling defineOutlookTools() and storing in this.tools, which is used by MCP request handlers.
    // Define the tools
    this.tools = defineOutlookTools();
  • Helper function that executes the underlying 'createEvent.vbs' VBScript file with the provided event details using the general executeScript utility.
    export async function createEvent(eventDetails) {
      return executeScript('createEvent', eventDetails);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates events but doesn't mention whether this requires authentication, what happens on conflicts, if notifications are sent to attendees, rate limits, or the response format. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

For a mutation tool with 10 parameters and no annotations or output schema, the description is insufficient. It doesn't address authentication needs, error conditions, what the return value contains, or how it interacts with sibling tools. The high parameter count and lack of structured behavioral data require more descriptive context than provided.

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?

The schema description coverage is 100%, with all 10 parameters well-documented in the input schema. The description adds no parameter-specific information beyond the generic 'create' action, so it doesn't enhance understanding of individual parameters. The baseline score of 3 reflects adequate but minimal value added by the description.

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 clearly states the verb ('create') and resource ('calendar event or meeting'), making the purpose unambiguous. However, it doesn't differentiate this tool from its sibling 'update_event' beyond the obvious creation vs. update distinction, nor does it specify if this is for personal calendars, shared calendars, or specific platforms.

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 like 'update_event' for modifying existing events or 'find_free_slots' for scheduling. It doesn't mention prerequisites (e.g., calendar access permissions) or contextual cues for when creation is appropriate versus listing or deleting events.

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/merajmehrabi/Outlook_Calendar_MCP'

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