Skip to main content
Glama

get_attendee_status

Check attendee response status for Outlook meetings to track who accepted, declined, or hasn't responded to an event invitation.

Instructions

Check the response status of meeting attendees

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent ID
calendarNoCalendar name (optional)

Implementation Reference

  • Core handler function that executes PowerShell script via Outlook COM interop to retrieve meeting details and attendee response statuses (Organizer, Tentative, Accepted, Declined, Not Responded).
    async getAttendeeStatus(options: {
      eventId: string;
      calendar?: string;
    }): Promise<any> {
      try {
        const script = `
          try {
            Add-Type -AssemblyName "Microsoft.Office.Interop.Outlook" -ErrorAction Stop
            $outlook = New-Object -ComObject Outlook.Application -ErrorAction Stop
            $namespace = $outlook.GetNamespace("MAPI")
            
            # Get appointment
            $appointment = $namespace.GetItemFromID("${options.eventId.replace(/"/g, '""')}")
            
            if (-not $appointment) {
              throw "Event not found with ID: ${options.eventId.replace(/"/g, '""')}"
            }
            
            # Check if it's a meeting
            if ($appointment.MeetingStatus -eq 0) { # olNonMeeting
              throw "The specified event is not a meeting"
            }
            
            # Get attendees
            $attendees = @()
            foreach ($recipient in $appointment.Recipients) {
              $responseStatus = switch ($recipient.MeetingResponseStatus) {
                1 { "Organizer" }
                2 { "Tentative" }
                3 { "Accepted" }
                4 { "Declined" }
                0 { "Not Responded" }
                default { "Unknown" }
              }
              
              $attendees += [PSCustomObject]@{
                Name = $recipient.Name
                Email = if ($recipient.Address) { $recipient.Address } else { $recipient.Name }
                ResponseStatus = $responseStatus
              }
            }
            
            # Build result
            $result = [PSCustomObject]@{
              Subject = $appointment.Subject
              Start = $appointment.Start.ToString("yyyy-MM-ddTHH:mm:ss")
              End = $appointment.End.ToString("yyyy-MM-ddTHH:mm:ss")
              Location = if ($appointment.Location) { $appointment.Location } else { "" }
              Organizer = if ($appointment.Organizer) { $appointment.Organizer } else { "" }
              Attendees = $attendees
            }
            
            Write-Output ($result | ConvertTo-Json -Compress -Depth 3)
            
          } catch {
            Write-Output ([PSCustomObject]@{
              Error = $_.Exception.Message
            } | ConvertTo-Json -Compress)
          }
        `;
    
        const result = await this.executePowerShell(script);
        const cleanResult = result.replace(/[\u0000-\u0008\u000B\u000C\u000E-\u001F\u007F]/g, '').trim();
        const data = JSON.parse(cleanResult);
    
        if (data.Error) {
          throw new Error(data.Error);
        }
    
        return data;
      } catch (error) {
        throw new Error(`Failed to get attendee status: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • src/index.ts:430-447 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema (requires eventId).
    {
      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"]
      }
    },
  • MCP server dispatch handler in CallToolRequest switch that calls the core getAttendeeStatus method and formats the response for the protocol.
    case 'get_attendee_status': {
      const attendeeStatus = await outlookManager.getAttendeeStatus({
        eventId: (args as any)?.eventId,
        calendar: (args as any)?.calendar
      });
      return {
        content: [
          {
            type: 'text',
            text: `👥 **Meeting Attendee Status**\n\n**Subject:** ${attendeeStatus.Subject}\n**Time:** ${attendeeStatus.Start} - ${attendeeStatus.End}\n**Location:** ${attendeeStatus.Location || 'N/A'}\n**Organizer:** ${attendeeStatus.Organizer}\n\n**Attendees:**\n` +
                 attendeeStatus.Attendees.map((attendee: any, index: number) => 
                   `${index + 1}. ${attendee.Name} (${attendee.Email})\n   Status: ${attendee.ResponseStatus}`
                 ).join('\n')
          },
        ],
      };
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.9/5.0
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.