Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Privileged Users

get_privileged_users
Read-only

Get all users who are members of privileged directory roles.

Instructions

Get all users who are members of privileged directory roles.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_privileged_users"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It confirms the tool enumerates role-member users, but says nothing about pagination, result size, or which roles count as 'privileged' — useful additions that are missing.

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 front-loaded sentence with no filler. For a parameterless read tool, this is exactly the right length and puts the resource scope first.

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 values are covered elsewhere, and with no parameters the surface area is small. The remaining gap is the undefined term 'privileged directory roles' — an agent cannot tell whether that means Global Admins only or all admin role assignments.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the description introduces no spurious inputs, so there is no parameter ambiguity. Baseline 4 applies since there is nothing for the description to clarify.

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 ('Get all users who are members of privileged directory roles'), which an agent can distinguish from search_users and get_user_by_id. It does not explicitly contrast with get_user_roles, so the boundary between the two is left to inference, but the scope is concrete.

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 phrase 'privileged directory roles' implies an access-review/audit use case, but the description never states when to prefer this over get_user_roles or search_users, nor any prerequisites such as required permissions. Usage is implied rather than directed.

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