IntuneRW-Core

Overview Schema Source Related Servers Discussions Admin

manage_intune_rbac

Create, update, delete, and list Intune RBAC role definitions and assignments to control user and group permissions with scope.

Instructions

Manage Intune RBAC role definitions and role assignments.

action values: list_roles — List all role definitions (built-in + custom) get_role — Get role definition details (role_id) create_role — Create a custom role (body) update_role — Update a custom role (role_id, body) delete_role — Delete a custom role (role_id, confirm=True) list_assignments — List all role assignments create_assignment — Assign role to user/group with scope (body) delete_assignment — Remove a role assignment (assignment_id, confirm=True) list_resource_operations — List all available RBAC resource actions (permission strings)

Input Schema

Name	Required	Description	Default
`top`	No
`body`	No
`action`	Yes
`confirm`	No
`role_id`	No
`assignment_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 21, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden for behavioral disclosure. It reveals that delete_role and delete_assignment require confirm=True, which is useful context for destructive operations. However, it does not mention side effects, permission requirements, or rate limits, leaving significant gaps.

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 concise and well-structured, with a summary line followed by a bulleted list of actions. Each line is informative and necessary, and the format makes it easy to scan. No wasted words.

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?

Although the tool is complex with 9 distinct actions, the description provides a high-level overview but omits details about body structures, return values, and edge-case behaviors. It is a useful starting point but not sufficient for an agent to invoke all actions without additional information.

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?

With 0% schema description coverage, the description adds meaning to action, role_id, assignment_id, and confirm by linking them to specific actions. However, 'body' is only vaguely described as the content for create/update, and 'top' is never explained. The description partially compensates for the schema gap but does not fully document all parameters.

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 tool manages Intune RBAC role definitions and assignments, with a specific list of actions (e.g., list_roles, get_role, create_role). This distinguishes it from sibling tools like manage_intune_devices or manage_entra_users, which target different resources.

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

Usage Guidelines3/5

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

The description implicitly indicates usage via the action list (e.g., 'create_role' for role creation), but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites (e.g., required permissions or when to prefer a different management tool).

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