Skip to main content
Glama
merajmehrabi

Outlook Calendar MCP

by merajmehrabi

get_attendee_status

Check the response status of meeting attendees in Outlook Calendar. Provide the event ID to retrieve attendee responses, ensuring effective meeting management without data leaving your local machine.

Instructions

Check the response status of meeting attendees

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarNoCalendar name (optional)
eventIdYesEvent ID

Implementation Reference

  • Full definition of the 'get_attendee_status' MCP tool, including schema, description, and handler function that executes the tool logic by calling getAttendeeStatus from scriptRunner.js and formatting the MCP response.
    get_attendee_status: {
      name: 'get_attendee_status',
      description: 'Check the response status of meeting attendees',
      inputSchema: {
        type: 'object',
        properties: {
          eventId: {
            type: 'string',
            description: 'Event ID'
          },
          calendar: {
            type: 'string',
            description: 'Calendar name (optional)'
          }
        },
        required: ['eventId']
      },
      handler: async ({ eventId, calendar }) => {
        try {
          const attendeeStatus = await getAttendeeStatus(eventId, calendar);
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(attendeeStatus, null, 2)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error getting attendee status: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    },
  • Input schema for the get_attendee_status tool defining parameters eventId (required) and calendar (optional).
    inputSchema: {
      type: 'object',
      properties: {
        eventId: {
          type: 'string',
          description: 'Event ID'
        },
        calendar: {
          type: 'string',
          description: 'Calendar name (optional)'
        }
      },
      required: ['eventId']
    },
  • Helper function getAttendeeStatus that executes the underlying VBScript 'getAttendeeStatus.vbs' via executeScript, invoked by the MCP tool handler.
    export async function getAttendeeStatus(eventId, calendar) {
      return executeScript('getAttendeeStatus', { eventId, calendar });
    }
  • src/index.js:34-36 (registration)
    Registration of all Outlook tools, including get_attendee_status, by calling defineOutlookTools() and storing in this.tools for use in MCP request handlers.
    // Define the tools
    this.tools = defineOutlookTools();
  • Core helper function executeScript used by getAttendeeStatus to run the VBScript implementation of attendee status checking.
    export async function executeScript(scriptName, params = {}) {
      return new Promise((resolve, reject) => {
        // Build the command with UTF-8 support
        const scriptPath = path.join(SCRIPTS_DIR, `${scriptName}.vbs`);
        let command = `chcp 65001 >nul 2>&1 && cscript //NoLogo "${scriptPath}"`;
        
        // Add parameters
        for (const [key, value] of Object.entries(params)) {
          if (value !== undefined && value !== null && value !== '') {
            // Handle special characters in values
            const escapedValue = value.toString().replace(/"/g, '\\"');
            command += ` /${key}:"${escapedValue}"`;
          }
        }
        
        // Execute the command with UTF-8 encoding
        exec(command, { encoding: 'utf8' }, (error, stdout, stderr) => {
          // Check for execution errors
          if (error && !stdout.includes(SUCCESS_PREFIX)) {
            return reject(new Error(`Script execution failed: ${error.message}`));
          }
          
          // Check for script errors
          if (stdout.includes(ERROR_PREFIX)) {
            const errorMessage = stdout.substring(stdout.indexOf(ERROR_PREFIX) + ERROR_PREFIX.length).trim();
            return reject(new Error(`Script error: ${errorMessage}`));
          }
          
          // Process successful output
          if (stdout.includes(SUCCESS_PREFIX)) {
            try {
              const jsonStr = stdout.substring(stdout.indexOf(SUCCESS_PREFIX) + SUCCESS_PREFIX.length).trim();
              const result = JSON.parse(jsonStr);
              return resolve(result);
            } catch (parseError) {
              return reject(new Error(`Failed to parse script output: ${parseError.message}`));
            }
          }
          
          // If we get here, something unexpected happened
          reject(new Error(`Unexpected script output: ${stdout}`));
        });
      });
    }
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 action ('Check') but doesn't describe what 'response status' entails (e.g., accepted, declined, tentative), whether it requires specific permissions, or how results are returned (e.g., as a list, with timestamps). This leaves significant gaps in understanding the tool's behavior beyond its basic purpose.

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 is front-loaded with the core action and resource, making it easy to parse. Every word earns its place, adhering to best practices for conciseness.

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 complexity (checking attendee statuses, which could involve permissions or data formats) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'response status' means, how results are structured, or any prerequisites like authentication. This leaves the agent with insufficient information to use the tool effectively in real scenarios.

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, with clear documentation for 'calendar' (optional calendar name) and 'eventId' (required event ID). The description doesn't add any meaning beyond this, such as explaining how 'calendar' affects the lookup or what format 'eventId' should be in. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 tool's purpose with a specific verb ('Check') and resource ('response status of meeting attendees'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_events' or 'get_calendars', which might also provide attendee information in different contexts, so it falls short of a perfect score.

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. For example, it doesn't specify if this is for checking statuses after an event, during planning, or how it differs from 'list_events' which might include attendee details. This lack of context leaves the agent to 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/merajmehrabi/Outlook_Calendar_MCP'

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