Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Create Group

create_group

Create a new group in Microsoft Graph.

Instructions

Create a new group in Microsoft Graph.

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": {
      "group_data": "<group_data>"
    },
    "name": "create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_dataYesDictionary containing group properties: - displayName: Display name of the group (required) - mailNickname: Mail alias for the group (required) - description: Description of the group (optional) - groupTypes: Array of group types e.g. ["Unified"] (optional) - mailEnabled: Whether the group is mail-enabled (optional) - securityEnabled: Whether the group is a security group (optional) - visibility: "Private" or "Public" for Microsoft 365 groups (optional) - owners: List of user IDs to add as owners (optional) - members: List of IDs to add as members (optional) - membershipRule: Rule for dynamic groups (required if DynamicMembership is in groupTypes) - membershipRuleProcessingState: "On" or "Paused" for dynamic groups (default: "On")

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered structurally. The description adds nothing beyond that: it doesn't say what happens on name collision, whether the caller becomes owner, what permissions are required, or whether the created object is returned.

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?

A single front-loaded sentence with zero filler. It is efficient, though the brevity leaves the gaps noted in other dimensions rather than being padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and a fully documented nested parameter mean the description needn't explain return values or field syntax. However, for a Graph group-creation mutation, the absence of any note on permissions, idempotency, or dynamic-group constraints leaves the definition minimally adequate.

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 description coverage is 100% and the group_data property is documented in detail (displayName, mailNickname, groupTypes, membershipRule, owners, members), so the schema does the heavy lifting. The description adds no supplementary semantics such as format conventions or defaults beyond what the schema already states.

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 a specific verb and resource ('Create a new group') plus the target system (Microsoft Graph), which is unambiguous against siblings like update_group and delete_group. It does not explicitly differentiate from other create_* tools or clarify scope, but the name/description pair is clear enough for selection.

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?

There is no guidance on when to use this versus update_group or the existing search_groups_by_name/get_group_by_id lookups, and no mention of prerequisites such as the permissions or consent needed to create groups in Graph. The agent must infer all of this.

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