Skip to main content
Glama
Sign In
wazuh-daily-triage

wazuh-daily-triage

by dururustem68
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

simulate_rule

Read-only

Replay a proposed child rule against recent real alerts to estimate daily alert volume, high-severity hits, affected agents/IPs/locations, and matched examples before submission.

Instructions

Replay a child-rule draft (if_sid) against the last N days of real alerts: estimated alerts/day it would take over, how many were at or above the high level, affected agents/IPs/locations, matched and unmatched examples. Use it before proposing a rule_draft and put the numbers in the proposal body.

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": {
      "xml": "<xml>"
    },
    "name": "simulate_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNoenvironment id (list_environments)
xmlYes
daysNo1-30, default 14

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, openWorldHint false), yet the description still adds real behavior: it replays against actual historical alerts rather than synthetic data, and it discloses the shape of the result (alerts/day, high-level counts, affected agents/IPs/locations, matched and unmatched examples). No output schema exists, so disclosing return content here is substantial value.

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?

Two sentences, front-loaded with the action and followed by the call-to-action; every clause maps to something the agent needs (inputs, outputs, next step). The output enumeration is dense but earns its place given there is no output schema.

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

Completeness4/5

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

For a read-only 3-parameter simulation tool with no output schema, the description covers the input constraint (if_sid child rule), the time window, the return contents, and the intended workflow. Only the days range/default and the demo-only env are left to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the 'xml' parameter carries no schema description, so the description compensates by defining it as a child-rule draft keyed on if_sid. It also restates 'last N days' which ties to the days parameter, though it does not mention the 1-30 bounds or the default.

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 ('Replay') and a specific resource ('a child-rule draft (if_sid) against the last N days of real alerts'), then enumerates what the replay yields. An agent can distinguish this from validate_rule_xml or rule_info without opening any schema.

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?

Explicitly says 'Use it before proposing a rule_draft and put the numbers in the proposal body,' giving a clear trigger and downstream use. It does not name exclusion cases or contrast with validate_rule_xml, but the when-to-use guidance is unambiguous.

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

Deploy Server

Other Tools