mcp-server-wazuh

List Agents

list_agents

Read-onlyIdempotent

Retrieve Wazuh manager agents with pagination, search, and status filters to inspect active, disconnected, pending, or never-connected endpoints.

Instructions

List agents from the Wazuh 5 manager API.

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": "list_agents"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size, from 1 to 100
`offset`	No	Result offset, from 0 to 10000
`search`	No	Optional manager search string, at most 200 characters
`status`	No	Optional agent status: active, disconnected, pending, or never_connected

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered elsewhere. The description adds nothing behavioral beyond that: no mention of pagination semantics, default page size behavior, rate limits, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its terseness borders on under-specification rather than optimal economy.

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?

With a full input schema, an output schema, and rich annotations, the description needs to carry less weight. Still, for a paginated list tool sitting among many search/list siblings, it omits any note on result ordering or how to choose between the two listing approaches.

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 100%, so limit, offset, search, and status are each documented with ranges, defaults, and allowed values. The description adds no extra meaning to any parameter, which is acceptable but earns only the baseline when the schema does all the work.

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?

The description names a specific verb and resource ("List agents") and identifies the source system (the Wazuh 5 manager API), so an agent knows exactly what it retrieves. It stops short of distinguishing this from siblings such as get_agents_summary or get_agent, leaving the boundary to be inferred.

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?

There is no guidance on when to call this instead of get_agents_summary, get_agent, or search_events. No exclusions, prerequisites, or context of use are mentioned.

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

Deploy Server