Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Detected Apps For Device

get_detected_apps_for_device
Read-only

Get applications detected on a specific Intune managed device (beta endpoint).

Instructions

Get applications detected on 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_detected_apps_for_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's main added value is the '(beta endpoint)' note, which warns of API instability. It says nothing about permissions, pagination, or whether results reflect last check-in versus real-time inventory.

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?

One front-loaded sentence with no filler; the resource, scope, and beta caveat all appear before any trailing detail.

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 covers return values and readOnlyHint covers safety, so the description only needed the scope and beta caveat it provides. Minor gaps remain around ID sourcing and result freshness.

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% for the single device_id parameter, so the description must compensate. It narrows the meaning to an Intune managed device identifier rather than a generic or Entra object ID, which is genuinely useful, but it gives no format or sourcing guidance.

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 ('applications detected on a specific Intune managed device'), which cleanly separates it from list_applications on the sibling list. The device-level scoping is explicit, though no sibling is named directly.

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 only implied: the 'specific Intune managed device' phrasing signals when it applies, but there is no statement of when to prefer this over list_applications or get_managed_device_by_id, and no prerequisites or exclusions.

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