Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Device Configuration States

get_device_configuration_states
Read-only

Get configuration-profile states for a specific Intune managed device (beta endpoint).

Instructions

Get configuration-profile states for a specific 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_device_configuration_states"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/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, so the description's main added value is the '(beta endpoint)' caveat, which usefully signals possible instability or differing behavior. It says nothing about pagination, response shape constraints, or permissions required to read Intune device state.

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 front-loaded sentence with zero filler; the scope and beta caveat are stated immediately. It is perhaps too terse for the information it needs to carry, but nothing is wasted or buried.

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 operation is a simple single-parameter read with readOnly annotation coverage. The remaining gaps are the ambiguity with sibling state/config tools and the undefined device_id, which are exactly what the description should have closed.

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% and the single parameter device_id is undocumented in the schema, so the description must compensate. It only implies that device_id refers to an Intune managed device (as opposed to an Entra device) and gives no format or source for that ID, e.g. whether it comes from get_all_managed_devices.

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 ('Get') and resource ('configuration-profile states') scoped to 'a specific Intune managed device', which is clearer than a bare restatement of the title. It does not differentiate from nearby siblings such as get_device_configurations or get_device_compliance_policy_states, leaving the agent to infer the distinction.

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 instead of get_device_configurations or get_device_compliance_policy_states, which are the most likely confusions. No prerequisites or exclusions are given, only the implicit 'you need a device'.

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