Outlook Assistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTLOOK_CLIENT_ID | Yes | The Application (client) ID from Azure Portal > App Registrations. | |
| OUTLOOK_CLIENT_SECRET | Yes | The client secret VALUE (not the Secret ID) from Azure Portal > App Registrations > Certificates & secrets. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aboutB | Returns information about this Outlook Assistant server |
| authenticateC | Authenticate with Microsoft Graph API to access Outlook data |
| check-auth-statusB | Check the current authentication status with Microsoft Graph API |
| list-eventsC | Lists upcoming events from your calendar |
| accept-eventC | Accepts a calendar event invitation |
| decline-eventC | Declines a calendar event |
| create-eventC | Creates a new calendar event |
| cancel-eventC | Cancels a calendar event |
| delete-eventC | Deletes a calendar event |
| list-emailsB | Lists recent emails from your inbox |
| search-emailsB | Search for emails using various criteria. Searches across ALL folders (inbox, archive, sent, etc.) by default. Specify folder to limit scope. |
| read-emailA | Reads the content of a specific email. Returns a short preview (255 chars) by default. Set fullBody=true to fetch the complete email body. |
| send-emailC | Composes and sends a new email |
| mark-as-readC | Marks an email as read or unread |
| list-foldersC | Lists mail folders in your Outlook account |
| create-folderC | Creates a new mail folder |
| move-emailsC | Moves emails from one folder to another |
| list-rulesC | Lists inbox rules in your Outlook account |
| create-ruleC | Creates a new inbox rule |
| edit-rule-sequenceC | Changes the execution order of an existing inbox rule |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Each tool has a clearly distinct purpose with no ambiguity, such as accept-event vs. decline-event for calendar responses, or list-emails vs. search-emails for email retrieval. The descriptions reinforce distinct actions on specific resources like events, emails, folders, and rules, ensuring agents can easily differentiate between tools.
All tool names follow a consistent verb_noun pattern with hyphens, such as create-event, list-folders, and mark-as-read. There are no deviations in naming conventions, making the set predictable and easy to parse for agents.
With 20 tools, the count is slightly high but reasonable for the Outlook domain, covering email, calendar, folders, and rules comprehensively. It includes core CRUD operations and management functions, though it might be borderline for some use cases due to the breadth.
The tool surface provides complete coverage for the Outlook domain, including CRUD operations for events, emails, folders, and rules, along with authentication and status checks. There are no obvious gaps, as it supports full lifecycle management from creation to deletion and search capabilities.