wazuh-daily-triage

logtest

Read-only

Test a log line against the Wazuh manager's current ruleset to identify the matching decoder, rule, and level; draft rules are not loaded.

Instructions

Run a log line through the manager's CURRENT ruleset (wazuh-logtest API) and see which decoder/rule/level matches. Cannot test a new draft rule (it is not loaded).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event": "<event>"
    },
    "name": "logtest"
  }
}

Input Schema

Name	Required	Description
`env`	No	environment id (list_environments)
`event`	Yes
`location`	No
`log_format`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.1Nov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the important constraint that evaluation happens against the live, currently loaded ruleset rather than pending changes. It also hints at the response shape (decoder/rule/level match), though it does not describe failure output when nothing matches.

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?

Two tight sentences: the capability and its scope are front-loaded, and the second sentence adds a non-obvious limitation rather than restating the name. Nothing is wasted.

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 no output schema, the description does at least sketch the return value (which decoder, rule, and level matched), which is the key thing an agent needs. However, three of four parameters are undocumented and there is no mention of what happens when no decoder or rule matches, leaving real gaps for a testing tool.

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?

Schema coverage is only 25%: only 'env' carries a description, while 'event', 'location', and 'log_format' are bare. The description's 'Run a log line' loosely maps to 'event' but adds no meaning for location or log_format (e.g., whether location sets the log source path that decoders key on), so it does not compensate for the documentation gap.

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?

States a specific verb and resource ('Run a log line through the manager's CURRENT ruleset'), names the underlying API (wazuh-logtest), and describes the outcome ('see which decoder/rule/level matches'). The contrast with a draft rule cleanly separates it from simulate_rule and validate_rule_xml.

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?

Gives an explicit exclusion: it cannot test a new draft rule because drafts are not loaded, which tells the agent when to reach for a draft-oriented sibling instead. It stops short of naming that sibling or spelling out prerequisites, so the routing is clear but not fully closed.

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

Deploy Server