Skip to main content
Glama
DynamicEndpoints

Microsoft 365 Bookings MCP Server

get_business_services

Retrieve the list of services available from a Microsoft Bookings business using its business ID to manage appointments and offerings.

Instructions

Get services offered by a Bookings business

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
businessIdYesID of the Bookings business

Implementation Reference

  • The handler function that executes the get_business_services tool. It queries the Microsoft Graph API for services of the specified booking business and returns the JSON response as text content.
    private async getBusinessServices(businessId: string) {
      const response = await this.graphClient
        .api(`/solutions/bookingBusinesses/${businessId}/services`)
        .get();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.value, null, 2),
          },
        ],
      };
  • Input schema definition for the get_business_services tool, specifying businessId as a required string.
    inputSchema: {
      type: 'object',
      properties: {
        businessId: {
          type: 'string',
          description: 'ID of the Bookings business',
        },
      },
      required: ['businessId'],
    },
  • src/index.ts:104-116 (registration)
    Tool registration in the tools array, including name, description, and input schema.
      name: 'get_business_services',
      description: 'Get services offered by a Bookings business',
      inputSchema: {
        type: 'object',
        properties: {
          businessId: {
            type: 'string',
            description: 'ID of the Bookings business',
          },
        },
        required: ['businessId'],
      },
    },
  • src/index.ts:151-154 (registration)
    Dispatch/registration in the switch statement for handling CallToolRequest for get_business_services.
    case 'get_business_services': {
      const args = request.params.arguments as { businessId: string };
      return await this.getBusinessServices(args.businessId);
    }
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 only states what the tool does without mentioning any behavioral traits like whether it's read-only, requires authentication, has rate limits, or what the return format might be. This is inadequate for a tool with no annotation coverage.

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 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?

Given the lack of annotations and output schema, the description is incomplete. It does not cover behavioral aspects, usage context, or what the tool returns, which are crucial for an agent to use it effectively. The description alone is insufficient for a tool with no structured data support.

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%, so the input schema already documents the single parameter 'businessId' with its type and description. The description does not add any additional meaning or context beyond what the schema provides, such as examples or constraints, resulting in a baseline score.

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 action ('Get') and resource ('services offered by a Bookings business'), making the purpose understandable. However, it does not differentiate from sibling tools like 'get_bookings_businesses' or 'get_business_staff', which also retrieve business-related data, so it lacks specificity in distinguishing its unique scope.

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, such as whether it should be used before or after other sibling tools like 'get_business_appointments'. There is no mention of prerequisites, exclusions, or contextual usage, leaving the agent without clear direction.

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