Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

List User Password Methods

list_user_password_methods
Read-only

List a user's password authentication methods.

Instructions

List a user's password authentication methods.

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": "list_user_password_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds nothing about what is returned (types of methods, ordering, empties) or about permissions required to read another user's auth methods. For a security-sensitive read, that is a notable gap beyond the annotation baseline.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler is well front-loaded, but its brevity here reflects under-specification rather than efficiency; the one sentence adds nothing the title did not already say.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 needn't be explained, but the definition still leaves the required user_id format undocumented and gives no route to the near-identical sibling. For a one-parameter read tool this is close to the minimum viable bar, but not above it.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter 'user_id' has no documented format in either the schema or the description. The description does not say whether this accepts an object ID/GUID, a UPN, or an email, which is the key ambiguity for this call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ('List') and resource ('a user's password authentication methods'), so the basic operation is clear. However, it is essentially a restatement of the tool title and does nothing to distinguish it from the sibling 'get_user_password_method', which appears to fetch a single method.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus 'get_user_password_method' or 'get_user_mfa_status'. The agent is left to infer the plural-list-vs-single-record distinction from the tool names alone.

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