Skip to main content
Glama
DynamicEndpoints

Microsoft 365 Bookings MCP Server

get_business_appointments

Retrieve scheduled appointments for a Microsoft Bookings business within a specified date range using business ID and optional start/end dates.

Instructions

Get appointments for a Bookings business

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
businessIdYesID of the Bookings business
startDateNoStart date for appointments (ISO format)
endDateNoEnd date for appointments (ISO format)

Implementation Reference

  • The handler function that fetches appointments for a Bookings business using Microsoft Graph API, with optional startDate and endDate filters.
    private async getBusinessAppointments(businessId: string, startDate?: string, endDate?: string) {
      let api = this.graphClient
        .api(`/solutions/bookingBusinesses/${businessId}/appointments`);
    
      if (startDate || endDate) {
        const filter = [];
        if (startDate) filter.push(`start ge ${startDate}`);
        if (endDate) filter.push(`end le ${endDate}`);
        api = api.filter(filter.join(' and '));
      }
    
      const response = await api.get();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.value, null, 2),
          },
        ],
      };
    }
  • Input schema defining parameters for the get_business_appointments tool: businessId (required), startDate and endDate (optional).
    inputSchema: {
      type: 'object',
      properties: {
        businessId: {
          type: 'string',
          description: 'ID of the Bookings business',
        },
        startDate: {
          type: 'string',
          description: 'Start date for appointments (ISO format)',
        },
        endDate: {
          type: 'string',
          description: 'End date for appointments (ISO format)',
        },
      },
      required: ['businessId'],
    },
  • src/index.ts:117-138 (registration)
    Tool registration in the ListTools response, including name, description, and input schema.
    {
      name: 'get_business_appointments',
      description: 'Get appointments for a Bookings business',
      inputSchema: {
        type: 'object',
        properties: {
          businessId: {
            type: 'string',
            description: 'ID of the Bookings business',
          },
          startDate: {
            type: 'string',
            description: 'Start date for appointments (ISO format)',
          },
          endDate: {
            type: 'string',
            description: 'End date for appointments (ISO format)',
          },
        },
        required: ['businessId'],
      },
    },
  • src/index.ts:155-166 (registration)
    Registration of the tool handler in the CallToolRequest switch statement.
    case 'get_business_appointments': {
      const args = request.params.arguments as {
        businessId: string;
        startDate?: string;
        endDate?: string;
      };
      return await this.getBusinessAppointments(
        args.businessId,
        args.startDate,
        args.endDate
      );
    }
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 a read operation ('Get') but doesn't cover critical aspects like authentication requirements, rate limits, pagination, error handling, or the format of returned data. This leaves significant gaps for an agent to understand how to interact with the tool effectively.

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, direct sentence with zero wasted words. It is appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary elaboration.

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 of a tool with three parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what data is returned, how appointments are filtered or sorted, or any behavioral traits, making it incomplete for effective agent use.

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, clearly documenting all three parameters (businessId, startDate, endDate) with their types and purposes. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 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 'Get' and the resource 'appointments for a Bookings business', making the purpose unambiguous. It distinguishes from sibling tools like 'get_bookings_businesses' by focusing on appointments rather than businesses, services, or staff, though it doesn't explicitly mention this distinction.

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 lacks context about prerequisites, such as needing a business ID from 'get_bookings_businesses', and doesn't mention any exclusions or specific scenarios for its use.

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

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/DynamicEndpoints/m365-bookings-mcp'

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