Skip to main content
Glama
DynamicEndpoints

Microsoft 365 Bookings MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MICROSOFT_GRAPH_CLIENT_IDYesYour Azure AD application client ID
MICROSOFT_GRAPH_TENANT_IDYesYour Azure AD tenant ID
MICROSOFT_GRAPH_CLIENT_SECRETYesYour Azure AD application client secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_bookings_businessesB

Get list of Bookings businesses

get_business_staffC

Get staff members for a Bookings business

get_business_servicesC

Get services offered by a Bookings business

get_business_appointmentsC

Get appointments for a Bookings business

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting different resources: businesses, appointments, services, and staff. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes like '_businesses' or '_business_appointments'. The naming is uniform and predictable across all four tools.

Tool Count3/5

With only 4 tools, the set feels thin for a Microsoft 365 Bookings domain, lacking essential operations like creating, updating, or deleting resources. While the tools cover basic retrieval, the scope is limited and may not support full agent workflows.

Completeness2/5

The toolset is severely incomplete, offering only read operations (get) with no ability to create, update, or delete bookings, appointments, services, or staff. This creates significant gaps that will cause agent failures in managing Bookings resources effectively.