Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Group Mfa Status

get_group_mfa_status
Read-only

Get MFA status for all members of a group.

Instructions

Get MFA status for all members of a group.

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": {
      "group_id": "<group_id>"
    },
    "name": "get_group_mfa_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYesThe unique identifier of the group.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description's burden is lighter. It adds nothing further — no note about result volume for large groups, pagination, or whether it requires directory-read permissions.

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 waste. Its terseness is efficient, though it leaves no room for the routing or scale caveats that would help an agent.

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?

An output schema exists, so return-value explanation isn't required, and the one-parameter read shape is simple. Still, for a tool that enumerates MFA status across an entire group, the absence of any note on result size or behavior with very large groups leaves a gap.

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 description coverage is 100% with a single required group_id, and the description adds no syntax or format details beyond the schema. Baseline 3 is appropriate when the schema fully carries parameter documentation.

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 MFA status') plus the scope ('all members of a group'), which is clear on its own. It stops short of explicitly naming get_user_mfa_status as the per-user counterpart, so sibling differentiation is left implicit.

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 'all members of a group' implies bulk/group-level usage versus the single-user sibling get_user_mfa_status, but no explicit when-to-use or when-not-to-use guidance is given. An agent must infer the choice from the wording.

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