Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
list_accountsB

List all signed-in Microsoft accounts

authenticate_accountA

Authenticate a new Microsoft account using device flow authentication

Returns authentication instructions and device code for the user to complete authentication. The user must visit the URL and enter the code to authenticate their Microsoft account.

complete_authenticationB

Complete the authentication process after the user has entered the device code

Args:
    flow_cache: The flow data returned from authenticate_account (the _flow_cache field)

Returns:
    Account information if authentication was successful
list_emailsC

List emails from specified folder

get_emailB

Get email details with size limits

Args:
    email_id: The email ID
    account_id: The account ID
    include_body: Whether to include the email body (default: True)
    body_max_length: Maximum characters for body content (default: 50000)
    include_attachments: Whether to include attachment metadata (default: True)
create_email_draftC

Create an email draft with file path(s) as attachments

send_emailC

Send an email immediately with file path(s) as attachments

update_emailC

Update email properties (isRead, categories, flag, etc.)

delete_emailC

Delete an email

move_emailC

Move email to another folder

reply_to_emailC

Reply to an email (sender only)

reply_all_emailC

Reply to all recipients of an email

list_eventsC

List calendar events within specified date range, including recurring event instances

get_eventC

Get full event details

create_eventC

Create a calendar event

update_eventD

Update event properties

delete_eventC

Delete or cancel a calendar event

respond_eventB

Respond to event invitation (accept, decline, tentativelyAccept)

check_availabilityC

Check calendar availability for scheduling

list_contactsD

List contacts

get_contactD

Get contact details

create_contactC

Create a new contact

update_contactD

Update contact information

delete_contactD

Delete a contact

list_filesC

List files and folders in OneDrive

get_fileC

Download a file from OneDrive to local path

create_fileC

Upload a local file to OneDrive

update_fileC

Update OneDrive file content from a local file

delete_fileC

Delete a file or folder

get_attachmentC

Download email attachment to a specified file path

search_filesC

Search for files in OneDrive using the modern search API.

search_emailsC

Search emails using the modern search API.

search_eventsC

Search calendar events using the modern search API.

search_contactsB

Search contacts. Uses traditional search since unified_search doesn't support contacts.

unified_searchB

Search across multiple Microsoft 365 resources using the modern search API

entity_types can include: 'message', 'event', 'drive', 'driveItem', 'list', 'listItem', 'site'
If not specified, searches across all available types.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 35 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific Microsoft 365 resources (contacts, emails, events, files) with clear action verbs, though some overlap exists between search_* tools and unified_search which could cause confusion about when to use which search method. The authentication tools (authenticate_account and complete_authentication) are clearly sequential rather than overlapping.

Naming Consistency5/5

Excellent consistency with a clear verb_noun pattern throughout all 35 tools (e.g., create_contact, delete_email, get_event, list_files, update_file). All tools use snake_case exclusively with no deviations in naming convention, making the tool set highly predictable and readable.

Tool Count3/5

35 tools is borderline heavy for a Microsoft 365 integration, though it covers multiple domains (authentication, contacts, email, calendar, OneDrive). The count feels somewhat excessive with separate search tools for each resource type plus a unified search, creating potential redundancy that could be streamlined.

Completeness5/5

Excellent coverage of Microsoft 365 domains with complete CRUD operations for contacts, emails, events, and files, plus comprehensive search capabilities and authentication workflow. The tool set provides full lifecycle management with no obvious gaps - agents can create, read, update, delete, list, and search across all supported resource types.

Maintenance

ActivityInactive
ResponsivenessUnresponsive