Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Search Users

search_users
Read-only

Find Microsoft Entra ID users by name or email and return a configurable number of matching results.

Instructions

Search for users by name or email.

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": {
      "query": "<query>"
    },
    "name": "search_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 10)
queryYesSearch query (name or email)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • changedOutput schema / properties / result / items / additionalProperties
      Previous value: -{
      -  "type": "string"
      -}New value: +true
  2. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/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 the description adds nothing further. It does not disclose matching semantics (substring vs exact, case sensitivity), how the default limit of 10 behaves, or whether results are truncated — the traits that actually matter for a search tool.

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 tight sentence with the resource and match scope front-loaded. Nothing is wasted, though the brevity comes at the cost of under-specification rather than efficient density.

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 no explanation, and the two parameters are fully documented in-schema. The gap is match semantics and result-limit behavior, which an agent needs to call a search tool correctly and which nothing in the structured fields supplies.

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 both parameters are documented in the schema. The description's 'by name or email' restates the schema's 'Search query (name or email)' rather than adding format or matching detail, 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?

Names a specific verb and resource ('Search for users') and scopes the match fields to name or email, which implicitly separates it from get_user_by_id. It never names a sibling outright, so an agent must infer the boundary with search_groups_by_name or get_privileged_users.

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 implied rather than stated: searching by name/email suggests using this when you lack a user ID, but the description never says so or points at alternatives like get_user_by_id. No exclusions or preconditions are given.

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