Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

groups

List, create, update, and delete Microsoft 365 groups, manage members and owners, and resolve SharePoint drives through Microsoft Graph.

Instructions

Microsoft 365 Groups: list, create, manage members and owners, resolve SharePoint drives

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoOData filter expression
ownersNoOwner user IDs (for create)
userIdNoUser ID (for add/remove member)
groupIdNoGroup ID
membersNoMember user IDs (for create)
operationYesOperation to perform
includeAllNoInclude all group types (not just M365)
maxResultsNoMax results (default: 25)
visibilityNoGroup visibility
descriptionNoGroup description
displayNameNoGroup display name
mailNicknameNoMail nickname (for create, no spaces)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must disclose behavior. It mentions create and member/owner management but never warns that update/delete exist, what permissions are needed, whether removals are reversible, or what side effects occur; operation-level requirements are left unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence with no filler and front-loads the resource. Its fragmentary list style is efficient, though the brevity comes at the cost of missing operational context rather than wasted wording.

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?

For a tool with 11 operations, 12 parameters, no annotations, and no output schema, the description is too thin. It omits update/delete behavior, permission needs, operation-specific requirements, and return semantics, so an agent cannot rely on it to invoke complex operations safely.

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?

Schema coverage is 100%, so all 12 parameters already carry descriptions and enum meanings. The description adds no parameter-level guidance such as required fields per operation or filter syntax, so it remains at the baseline for a fully documented schema.

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?

States the resource (Microsoft 365 Groups) and enumerates core capabilities: list, create, manage members and owners, and resolve SharePoint drives. It is distinguishable from siblings such as calendar or mail, but the capability list is broad and omits operations like get/update/delete that are present in the schema.

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 only lists capabilities; it gives no when-to-use guidance, prerequisites, or alternatives for overlapping group/drive operations. An agent must infer which operation to use from the enum alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.