Skip to main content
Glama
DynamicEndpoints

Microsoft 365 Bookings MCP Server

get_bookings_businesses

Retrieve all Microsoft Bookings businesses to manage appointments, staff, and services through the Graph API.

Instructions

Get list of Bookings businesses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core implementation of the 'get_bookings_businesses' tool. It queries the Microsoft Graph API endpoint '/solutions/bookingBusinesses', retrieves the list of booking businesses, and returns the JSON-formatted response as MCP tool content.
    private async getBookingsBusinesses() {
      const response = await this.graphClient
        .api('/solutions/bookingBusinesses')
        .get();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.value, null, 2),
          },
        ],
      };
    }
  • src/index.ts:81-88 (registration)
    Registration of the 'get_bookings_businesses' tool in the ListToolsRequestSchema handler. Defines the tool name, description, and input schema (no required parameters).
    {
      name: 'get_bookings_businesses',
      description: 'Get list of Bookings businesses',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for the 'get_bookings_businesses' tool, specifying an empty object (no input parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • src/index.ts:145-146 (registration)
    Dispatch logic in the CallToolRequestSchema handler that routes calls to the 'get_bookings_businesses' tool to its handler function.
    case 'get_bookings_businesses':
      return await this.getBookingsBusinesses();
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits like pagination, rate limits, authentication needs, or return format. It's minimal and lacks critical operational details.

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 any wasted words. It's front-loaded and appropriately sized for a simple tool.

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 no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It fails to provide necessary context like what data is returned, how results are structured, or any operational constraints, leaving significant gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter info, which is appropriate here, but a perfect score is reserved for cases where it adds value beyond schema.

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 resource 'list of Bookings businesses', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like get_business_appointments, get_business_services, or get_business_staff, which prevents 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?

No guidance is provided on when to use this tool versus the sibling tools. The description lacks context about alternatives or specific use cases, leaving the agent without direction on tool selection.

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