Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get User Mfa Status

get_user_mfa_status
Read-only

Get MFA status and methods for a specific user.

Instructions

Get MFA status and methods for a specific user.

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_mfa_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe unique identifier of the user.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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, and an output schema covers the return shape. The description adds nothing beyond that – no note on permissions required, what 'methods' include, or behavior for users without MFA enrolled.

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 padding. It is efficient, though its brevity comes at the cost of the sibling differentiation noted elsewhere.

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?

For a one-parameter read tool with readOnlyHint and a full output schema, this is close to complete. The only meaningful omission is routing guidance relative to get_group_mfa_status and related MFA/password-method siblings.

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?

Only one parameter with 100% schema description coverage; the schema already defines user_id as 'the unique identifier of the user'. The description adds no format or sourcing guidance (e.g., object ID vs UPN), so baseline 3 applies.

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+resource ('Get MFA status and methods') scoped to 'a specific user', which implicitly separates it from get_group_mfa_status. However, it never names the sibling or states the distinction, so differentiation rests on the reader noticing 'user' vs 'group'.

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?

Usage is only implied by the tool name and the word 'specific user'. There is no explicit when-to-use, when-not, or pointer to the sibling get_group_mfa_status for group-level MFA.

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