Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get User Groups

get_user_groups
Read-only

Get all groups (including transitive memberships) for a user by user ID.

Instructions

Get all groups (including transitive memberships) for a user by user ID.

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": {
      "user_id": "<user_id>"
    },
    "name": "get_user_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint already declares the safety profile, so the description's value-add is the disclosure that transitive memberships are expanded — that signals a potentially larger/recursive result set than a direct-membership call. It doesn't cover behavior on unknown user IDs or any result-size/pagination limits.

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?

A single sentence with zero filler, front-loading the resource scope and then the transitive qualifier. Nothing to trim.

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?

An output schema exists, so return shape needn't be explained, and the call surface is a single required ID. The description is adequate for calling it, though it omits whether the ID must be an object ID/UPN and what happens for an unknown user.

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 0%, but there is only one parameter and the description's phrase 'by user ID' identifies it as a user identifier, matching the schema's user_id. It adds no format, source, or example beyond the name itself.

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 (get), resource (groups), scoping key (by user ID), and a meaningful qualifier (transitive memberships), so it is distinguishable from get_all_groups and get_group_members. It does not explicitly contrast with the closest sibling, get_user_roles.

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 'for a user by user ID' framing implies the usage context, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., get_all_groups for tenant-wide listings, get_user_roles for role assignments). Routing is left to inference.

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