wazuh-mcp

List agent groups

wazuh_list_groups

Read-onlyIdempotent

Lists Wazuh agent groups with member counts and configuration checksums. Optionally, provide a group name to list its member agents.

Instructions

List configured agent groups with their member counts and configuration checksums. Pass a group name to list its members instead.

Input Schema

TableJSON Schema

Name	Required	Description
`group`	No	If set, list the agents belonging to this group.
`limit`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The description discloses the conditional output behavior and is consistent with the readOnly, idempotent, and non-destructive annotations. It does not mention pagination details, but the annotations already cover the main safety aspects.

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?

The description is concise, using two sentences to convey the purpose and conditional behavior without extraneous detail.

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?

The description covers the core purpose and a key conditional behavior, and output schema is present. However, missing parameter semantics for pagination and lack of usage-selection guidance leave some context gaps.

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?

Only the 'group' parameter is described; 'limit' and 'offset' are not mentioned. With schema coverage at 33%, the description adds some value for one parameter but leaves most parameter semantics undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists configured agent groups with member counts and checksums, and explicitly covers the conditional behavior of listing members when a group name is supplied. The verb and resource are specific.

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 explicit guidance is given for when to use this tool versus alternative sibling tools. The conditional note about passing a group name is useful but does not address tool selection or boundary conditions.

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