Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get User By Id

get_user_by_id
Read-only

Get a specific user by their ID.

Instructions

Get a specific user by their ID.

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

Input Schema

NameRequiredDescriptionDefault
user_idYesThe unique identifier (ID) of the user.

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?

Annotations already declare readOnlyHint=true, so safety is covered. The description adds nothing beyond that: it does not mention behavior when the ID is unknown (empty result vs. error), required permissions, or any tenant scoping, which are the kinds of details that would add value here.

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 short sentence with no filler, and the resource and key are front-loaded. It is efficient but so terse that it borders on under-specification rather than crispness.

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 values need not be explained, and the tool is simple (one required param). Still, with many sibling lookup tools, the description leaves an agent without routing guidance or edge-case behavior, so it is only minimally complete.

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%, and the single user_id parameter is documented as 'The unique identifier (ID) of the user.' The description adds no format hints (GUID vs. UPN) or examples, so the schema does all the work — baseline 3 is appropriate.

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 and resource ('get a specific user') and echoes the ID lookup, but it is essentially a restatement of the tool name and title with no distinguishing detail. It does not differentiate itself from the sibling search_users, which an agent could easily confuse with a single-user lookup.

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 search_users or other user-related siblings like get_user_sign_ins. Usage is only implied by the name; nothing tells the agent the precondition that it already has a user ID.

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