wazuh-mcp

List Wazuh agents

wazuh_list_agents

Read-onlyIdempotent

List and filter Wazuh agents by status, group, version, or platform. Supports server-side filtering, sorting, and paging for precise endpoint queries.

Instructions

List and filter agents enrolled with the Wazuh manager. Use this to answer 'which endpoints are disconnected', 'what agents are in group X', or 'which agents run an outdated version'. Supports server-side filtering, sorting and paging.

Input Schema

TableJSON Schema

Name	Required	Description
`ip`	No	Exact agent IP match.
`name`	No	Exact agent name match.
`sort`	No	Sort field prefixed with '-' for descending, e.g. '-lastKeepAlive'.
`group`	No	Only agents in this group.
`limit`	No	Max agents to return.
`query`	No	Raw Wazuh query filter for conditions the named arguments do not cover, e.g. "os.platform=linux;rule.level>10". Use ';' for AND, ',' for OR.
`offset`	No	Paging offset.
`search`	No	Free-text substring match across agent fields.
`status`	No	Restrict to these connection states.
`version`	No	Agent version, e.g. 'v4.9.0'.
`os_platform`	No	OS platform, e.g. 'linux', 'windows', 'darwin'.

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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description reinforces the read-only nature by saying 'List and filter' and adds context about server-side filtering, sorting, and paging. It does not contradict the annotations, though it does not discuss auth needs or rate limits, which are less critical given the annotations.

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 three concise sentences with no filler. The main purpose is front-loaded, followed by concrete use cases and a brief note on supported features. It is easy to parse and directly useful to an agent.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich parameter schema, clear annotations, and the presence of an output schema, the description provides sufficient context: it states what the tool does, gives example use cases, and notes filtering/sorting/paging support. No critical contextual information is missing.

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?

All 11 parameters have individual schema descriptions, giving 100% schema description coverage. The description adds no additional parameter-level details beyond what the schema already provides, so the baseline score of 3 is appropriate.

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's purpose: 'List and filter agents enrolled with the Wazuh manager.' It includes concrete example questions ('which endpoints are disconnected', 'what agents are in group X', 'which agents run an outdated version') and distinguishes this list/filter tool from singular agent lookup or agent-related summary tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit use cases with 'Use this to answer...' and mentions server-side filtering, sorting, and paging. It does not explicitly mention when not to use this tool or compare it to alternative tools, but the provided examples are strong enough for an agent to select it appropriately.

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