mcp-server-wazuh

Search Events

search_events

Read-onlyIdempotent

Query the Wazuh events data stream on the indexer to retrieve and filter security events by OpenSearch query string and optional agent ID, with pagination for manageable results.

Instructions

Search the wazuh-events-v5 data stream on the indexer.

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

Input Schema

Name	Required	Description
`limit`	No	Page size, from 1 to 100
`query`	No	OpenSearch query_string. Empty matches all events.
`offset`	No	Result offset, from 0 to 10000
`agent_id`	No	Optional agent id filter

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, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the location phrase 'on the indexer' and says nothing about result volume, sorting, pagination behavior, or performance implications of an unfiltered query, which is real missed context.

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

Conciseness3/5

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

A single front-loaded sentence with zero filler, which is structurally sound. It is arguably too sparse for a search tool with four paging/query parameters, so brevity here borders on under-specification.

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 an output schema present and full schema description coverage, the description needn't explain return values or parameters. Still, for an open-world search over a specific index it ought to say something about default behavior, max result windows, or how it differs from the other search_* tools, none of which is present.

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 100%, so limit, query, offset and agent_id are all documented in the input schema, giving a baseline of 3. The description contributes no additional meaning about query syntax, filter interaction, or paging limits beyond what the schema already states.

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 states a specific verb (Search) and names the concrete target resource, the wazuh-events-v5 data stream on the indexer. It does not, however, contrast itself with the sibling search_* tools (search_mitre, search_findings, search_vulnerabilities), leaving the agent to infer that this one covers general security events.

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 when-to-use guidance, no when-not-to-use guidance, and no mention of the alternative search tools in the sibling list. The only usage hint (empty query matches all events) lives in the schema, not the description.

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

Deploy Server