Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Device Compliance Policy States

get_device_compliance_policy_states
Read-only

Get compliance-policy states for a specific Intune managed device (beta endpoint).

Instructions

Get compliance-policy 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_compliance_policy_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.2/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. The description adds one genuinely useful behavioral detail: it targets the beta endpoint, signaling possible instability. It does not mention permission requirements or behavior for unknown/non-compliant device IDs.

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 front-loaded sentence with zero filler, and the beta-endpoint caveat is tucked into a parenthetical where it doesn't distract. Slightly terse for the amount of information an agent needs, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 with one required parameter the surface is small. What's missing is minor: how to source the device_id and any note on beta-endpoint reliability or empty results.

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 coverage is 0% and the single device_id property has no description, so the description must compensate. Saying 'for a specific Intune managed device' clarifies that device_id is an Intune managed-device identifier, but it gives no format hint or pointer to get_managed_device_by_id for obtaining one.

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 compliance-policy states') scoped to an Intune managed device. It implicitly distinguishes itself from the nearby 'get_device_compliance_policies' by returning per-device states rather than policy definitions, but it never names that sibling to make the distinction explicit.

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 when-to-use guidance, no exclusions, and no mention of the closely related siblings (get_device_compliance_policies, get_device_configuration_states). The agent must infer the use case 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.