Skip to main content
Glama

cipp_create_group

DestructiveIdempotent

Create a group in a Microsoft 365 tenant for RBAC, Conditional Access, or mail distribution. Operation is reversible by deleting the group.

Instructions

⚠ HIGH-IMPACT. Creates a new group in the tenant, which can be used for security policy assignments (RBAC, Conditional Access) or mail distribution. Reversible by deleting the group. Confirm with the user before invoking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoOptional free-text description of the group purpose.
displayNameYesHuman-readable name for the new group.
mailEnabledNoWhen true, the group is mail-enabled and can receive email. Required for Microsoft 365 groups.
mailNicknameNoThe mail alias used as the local part of the group email address (e.g. "finance-team" for finance-team@contoso.com). Required when mailEnabled is true.
tenantFilterYesTenant domain name or ID to scope the operation. Use 'allTenants' to target every managed tenant.
securityEnabledNoWhen true, the group can be used for security policy assignments (RBAC, Conditional Access, etc.).
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds context by labeling it 'HIGH-IMPACT,' stating it's reversible by deletion, and requiring user confirmation. This goes beyond annotations, providing behavioral expectations.

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

Conciseness5/5

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

The description is extremely concise: one sentence plus an impactful warning. It front-loads the severity, making it efficient for an agent to parse.

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

Completeness4/5

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

Without an output schema, the description adequately covers purpose, impact, and reversibility. For a creation tool with moderate complexity, it provides sufficient context for an agent to understand the tool's role.

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 the description adds no extra parameter meaning. Baseline score of 3 is appropriate since the schema fully documents each parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'creates' and resource 'group', and specifies use cases (security policy assignments or mail distribution). It effectively distinguishes from sibling tools like cipp_list_groups or cipp_create_user.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises 'Confirm with the user before invoking,' providing a clear usage guideline. It implies caution due to high impact but does not explicitly list when not to use or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/cipp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server