Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get User Password Method

get_user_password_method
Read-only

Get a specific password authentication method for a user.

Instructions

Get a specific password authentication method for a 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>",
      "method_id": "<method_id>"
    },
    "name": "get_user_password_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
method_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

readOnlyHint=true already establishes this as a safe read, and the description adds nothing beyond that – no indication of required permissions, whether credential-sensitive fields are returned, or error behavior when the method does not exist. For a tool touching password methods, the silence on sensitive-data handling is a real gap.

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 no filler. It is efficient, though its brevity contributes to the missing guidance elsewhere.

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 with 0% schema coverage the description should at least describe identifier formats and any access requirements. It leaves the agent guessing on both.

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%, so neither parameter is documented anywhere, yet the description only implies them via 'for a user' and 'specific ... method'. Crucially, it doesn't say whether user_id accepts a UPN/email or an object ID, or what form method_id takes.

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 a password authentication method) scoped to a user, which cleanly separates it from list_user_password_methods. It never names that sibling, though, so the differentiation is inferred rather than explicit.

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?

No guidance on when to use a single-item get versus the sibling list_user_password_methods, and no mention of the related mutation tool reset_user_password_direct. The agent must infer the retrieval workflow entirely from the name.

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