Skip to main content
Glama
merajmehrabi

Outlook Calendar MCP

by merajmehrabi

find_free_slots

Identify open time slots in your Outlook Calendar between specified dates with customizable work hours and duration, ensuring efficient scheduling without data leaving your system.

Instructions

Find available time slots in the calendar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarNoCalendar name (optional)
durationNoDuration in minutes (optional, defaults to 30)
endDateNoEnd date in MM/DD/YYYY format (optional, defaults to 7 days from start date)
startDateYesStart date in MM/DD/YYYY format
workDayEndNoWork day end hour (0-23) (optional, defaults to 17)
workDayStartNoWork day start hour (0-23) (optional, defaults to 9)

Implementation Reference

  • The MCP handler function for the 'find_free_slots' tool. It calls findFreeSlots from scriptRunner.js, formats the result as MCP content, and handles errors.
    handler: async ({ startDate, endDate, duration, workDayStart, workDayEnd, calendar }) => {
      try {
        const freeSlots = await findFreeSlots(startDate, endDate, duration, workDayStart, workDayEnd, calendar);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(freeSlots, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error finding free slots: ${error.message}`
            }
          ],
          isError: true
        };
      }
  • Input schema defining the parameters and validation for the 'find_free_slots' tool.
    inputSchema: {
      type: 'object',
      properties: {
        startDate: {
          type: 'string',
          description: 'Start date in MM/DD/YYYY format'
        },
        endDate: {
          type: 'string',
          description: 'End date in MM/DD/YYYY format (optional, defaults to 7 days from start date)'
        },
        duration: {
          type: 'number',
          description: 'Duration in minutes (optional, defaults to 30)'
        },
        workDayStart: {
          type: 'number',
          description: 'Work day start hour (0-23) (optional, defaults to 9)'
        },
        workDayEnd: {
          type: 'number',
          description: 'Work day end hour (0-23) (optional, defaults to 17)'
        },
        calendar: {
          type: 'string',
          description: 'Calendar name (optional)'
        }
      },
      required: ['startDate']
    },
  • Helper function findFreeSlots that executes the underlying VBScript 'findFreeSlots.vbs' via executeScript.
    export async function findFreeSlots(startDate, endDate, duration, workDayStart, workDayEnd, calendar) {
      return executeScript('findFreeSlots', {
        startDate,
        endDate,
        duration,
        workDayStart,
        workDayEnd,
        calendar
      });
    }
  • src/index.js:35-36 (registration)
    Registration of all tools including 'find_free_slots' by calling defineOutlookTools() and storing in this.tools for use in MCP request handlers.
    this.tools = defineOutlookTools();
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 but only states the basic action. It doesn't cover critical aspects like whether this is a read-only operation, how results are formatted, if there are rate limits, or authentication requirements, leaving significant gaps for an agent to understand tool behavior.

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 purpose without unnecessary words. It's front-loaded and appropriately sized for a simple query tool, with no wasted information.

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 tool's moderate complexity (6 parameters, no output schema, and no annotations), the description is incomplete. It fails to explain return values, error conditions, or behavioral traits, making it inadequate for an agent to fully understand how to use this tool effectively in context.

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 input schema has 100% description coverage, so parameters like 'duration', 'workDayStart', and 'endDate' are well-documented there. The description adds no additional parameter semantics beyond implying time slot availability, which aligns with the schema but doesn't provide extra value, meeting the baseline for high schema coverage.

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 ('Find') and resource ('available time slots in the calendar'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling tools like 'list_events' or 'get_calendars' that might also involve calendar queries, missing full differentiation.

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 'list_events' or 'get_calendars' from the sibling list. It lacks context about prerequisites, such as needing calendar access or when free slot queries are appropriate over other calendar operations.

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