Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Managed Device By Id

get_managed_device_by_id
Read-only

Get full details of a single Intune managed device (beta endpoint).

Instructions

Get full details of a single Intune managed device (beta endpoint).

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": {
      "device_id": "<device_id>"
    },
    "name": "get_managed_device_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context that this uses the beta endpoint, which signals possible API instability, but it does not describe permission requirements, beta limitations, or other behavioral traits.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no wasted words. It states the core purpose and the beta-endpoint caveat directly.

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-value details need not be in the description, and the readOnlyHint covers safety. However, for a lookup tool with an undocumented required identifier parameter, the description should say more about what the device_id represents and whether the beta endpoint imposes constraints.

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?

The only parameter, device_id, has 0% schema description coverage, and the description does not explain its format or source (for example, whether it is an Intune device ID or an Entra object ID). The description's 'by id' phrasing only restates the parameter name without compensating for the schema gap.

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?

The description clearly states a specific verb and resource: 'Get full details of a single Intune managed device.' It distinguishes the single-device scope from list-oriented siblings such as get_all_managed_devices and get_managed_devices_by_user, though it does not name those siblings explicitly.

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?

The phrase 'single Intune managed device' implies this is for fetching one device by identifier rather than listing devices, but there are no explicit when-to-use or when-not-to-use guidelines, and no sibling tool is named as an alternative.

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