Skip to main content
Glama
m365-organizer

m365-organizer

by Denovarix

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
client_idYesThe client ID of your Entra app registration (configured in ~/.m365-organizer/config.json)
tenant_idNoThe tenant ID; use 'consumers' for personal Microsoft accounts (configured in ~/.m365-organizer/config.json)consumers

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
mail_folder_treeA

List every mail folder with its path, total and unread counts.

mail_create_folderB

Create a nested mail folder path like 'Work/Clients/Acme'. Returns the leaf id.

mail_sender_statsC

Top senders and domains in a folder. sample limits how many messages to scan (0 = all).

mail_move_from_sendersC

Bulk-move existing mail from addresses or '@domain' entries into dest_path (created if missing).

mail_list_rulesB

List inbox rules.

mail_add_sender_ruleC

Create an inbox rule routing future mail from senders/domains into dest_path.

mail_delete_ruleC

Delete an inbox rule.

drive_listB

List OneDrive items at a folder path ('' = root).

drive_create_folderB

Create a nested OneDrive folder path. Returns id.

drive_moveB

Move a OneDrive item into dest_path (created if missing).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct resource and action, and the mail_/drive_ prefixes separate the two domains cleanly. The only near-pair, mail_move_from_senders (existing mail) vs mail_add_sender_rule (future mail via rule), is explicitly differentiated in the descriptions.

Naming Consistency4/5

All names use snake_case with a consistent domain prefix (mail_/drive_) followed by a verb_noun pattern (create_folder, list_rules, delete_rule, move). The exceptions are the noun-phrase names mail_folder_tree and mail_sender_stats, which deviate from the verb-first convention but remain readable.

Tool Count5/5

Ten tools is well within the ideal range and each earns its place: seven cover mail structure, bulk moves, and rule automation; three cover drive listing, folder creation, and moves. Nothing looks redundant or padded.

Completeness4/5

Mail side is strong (tree, create, stats, bulk move, rule list/add/delete), but has no folder delete/rename or rule update. The drive surface is noticeably thinner — list, create, move only, with no delete or rename, which limits cleanup workflows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues