Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get All Managed Devices

get_all_managed_devices
Read-only

Get all managed devices (optionally filter by OS).

Instructions

Get all managed devices (optionally filter by OS).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_managed_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
filter_osNo

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?

The readOnlyHint annotation already declares this is a non-destructive read. The description adds only that filtering is optional; it says nothing about result size, pagination, required permissions, or throttling, which matter for a tenant-wide device listing.

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?

A single short sentence with the resource and the optional filter front-loaded; no filler or redundancy.

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?

For a simple read-only listing tool with an output schema, the description covers the essential behavior. The remaining gap is the meaning and accepted values of filter_os, plus how large result sets are handled.

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 description coverage is 0%, so the description must carry the parameter burden. It does convey that filter_os filters by operating system and is optional, but gives no accepted values, format, or matching behavior (exact vs partial), so the semantics remain thin.

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 ('all managed devices') with an explicit scope ('all'), which distinguishes it from get_managed_devices_by_user and get_managed_device_by_id. It does not name those siblings explicitly, but the 'all' scope makes the distinction inferable.

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 parenthetical '(optionally filter by OS)' implies the usage pattern of listing everything or narrowing by OS, but there is no explicit guidance on when to prefer this over get_managed_devices_by_user, nor any exclusion or prerequisite information.

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