Skip to main content
Glama
DynamicEndpoints

Microsoft 365 Bookings MCP Server

get_business_staff

Retrieve staff members for a Microsoft Bookings business using its business ID to manage team assignments and scheduling.

Instructions

Get staff members for a Bookings business

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
businessIdYesID of the Bookings business

Implementation Reference

  • Executes the get_business_staff tool logic by querying the Microsoft Graph API for staff members of the specified booking business and returning the result as JSON text.
    private async getBusinessStaff(businessId: string) {
      const response = await this.graphClient
        .api(`/solutions/bookingBusinesses/${businessId}/staffMembers`)
        .get();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.value, null, 2),
          },
        ],
      };
    }
  • src/index.ts:89-102 (registration)
    Registers the get_business_staff tool in the MCP server's tool list, providing name, description, and input schema.
    {
      name: 'get_business_staff',
      description: 'Get staff members for a Bookings business',
      inputSchema: {
        type: 'object',
        properties: {
          businessId: {
            type: 'string',
            description: 'ID of the Bookings business',
          },
        },
        required: ['businessId'],
      },
    },
  • Input schema for the get_business_staff tool, requiring a businessId string.
    inputSchema: {
      type: 'object',
      properties: {
        businessId: {
          type: 'string',
          description: 'ID of the Bookings business',
        },
      },
      required: ['businessId'],
    },
  • Dispatches the CallToolRequest for get_business_staff to the handler function, extracting businessId from arguments.
    case 'get_business_staff': {
      const args = request.params.arguments as { businessId: string };
      return await this.getBusinessStaff(args.businessId);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Get' which implies a read operation, but doesn't disclose behavioral traits such as permissions needed, rate limits, pagination, or response format. 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, clear sentence with no wasted words. It's appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary detail.

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 and no output schema, the description is incomplete. It lacks information on behavioral aspects, response format, and usage context, which are crucial for an agent to effectively invoke this tool in a real-world scenario.

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%, with the parameter 'businessId' fully documented in the schema. The description doesn't add any meaning beyond what the schema provides, such as examples or constraints, so it meets the baseline 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 action ('Get') and resource ('staff members for a Bookings business'), making the purpose understandable. However, it doesn't differentiate from sibling tools like get_business_appointments or get_business_services, which also retrieve business-related data, so it misses full sibling 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 doesn't mention prerequisites, context, or exclusions, leaving the agent without usage direction beyond the basic purpose.

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