List all management groups to scope instructions to device sets. Retrieve device groups for targeting instructions across your DEX tenant.
List all Management Groups (device groups). These are used to scope instructions to sets of devices.
| Name | Required | Description | Default |
|---|---|---|---|
| includeSystemGroups | No | Include built-in system groups (default false) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations available, the description carries the full burden for behavioral disclosure. 'List all' signals a read-only listing operation, but the description does not mention whether results are paginated, how system groups behave beyond the schema's default, or what fields the returned groups contain. The purpose context is helpful but behavioral detail is minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no filler. The primary action is front-loaded, the useful clarification 'device groups' is included, and the context sentence about scoping instructions earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a low-complexity list operation with one optional boolean parameter and no nested structures. The description plus schema are enough for an agent to invoke it correctly. Some output-shape details are missing, but for a simple 'list all' endpoint this is a minor gap rather than a critical omission.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the single optional parameter includeSystemGroups is already well documented in the schema. The tool description adds nothing about parameters, but the schema already provides sufficient meaning, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the action ('List all Management Groups') and the resource ('Management Groups (device groups)'), with an additional context note about how they are used. It is distinguishable from sibling tools like management_groups_get_by_id or management_groups_search because it explicitly says 'list all', though it does not name those alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'List all Management Groups' implies when to use it, and the note about scoping instructions gives useful context. However, there is no explicit guidance about when to choose this over management_groups_search, get_by_id, or get_by_name, and no exclusions or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.