Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Managed Devices By User

get_managed_devices_by_user
Read-only

Get all managed devices for a specific userId.

Instructions

Get all managed devices for a specific userId.

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

Input Schema

NameRequiredDescriptionDefault
user_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

readOnlyHint=true already establishes this is a safe read, and an output schema exists to describe returns, so the description's burden is light. However, it adds nothing beyond that: no pagination behavior, no mention of what happens if the user has no devices or does not exist, and no volume expectations for a device-list endpoint.

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?

One sentence, front-loaded with the verb and resource, and nothing redundant. It is efficient but borders on under-specified rather than tight.

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?

Annotations cover the safety profile and an output schema covers return shape, so the essentials are present. Still missing for a filtered-list tool: identifier format for user_id and whether results are paginated or empty-list on no matches.

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 coverage is 0% for the single required user_id parameter, so the description must carry the semantics. It only restates the parameter name as 'specific userId' and gives no format (GUID vs UPN vs object ID) or validation rule, leaving the agent to guess the identifier type.

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 all managed devices') plus the scoping dimension ('for a specific userId'), which distinguishes it from get_all_managed_devices and get_managed_device_by_id. It doesn't name those siblings explicitly, so differentiation is inferable rather than stated.

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 this versus get_all_managed_devices (all devices) or get_managed_device_by_id (single device). The agent must infer the selection rule from the name alone.

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