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

wazuh-daily-triage

by dururustem68
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

rule_info

Read-only

Retrieves Wazuh rule definitions by ID, including level, description, file, groups, and conditions, to support alert triage and investigation.

Instructions

Rule definitions (level, description, file, groups, conditions).

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": {
      "rule_ids": "<rule_ids>"
    },
    "name": "rule_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNoenvironment id (list_environments)
rule_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint=false annotations already establish the safe, closed-world nature of the operation. The description adds the returned field list, which is useful, but does not disclose behavior for invalid or missing rule_ids, environment scoping, or result ordering.

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?

The description is a single front-loaded fragment with no wasted wording. It is concise and structurally easy to scan, though that conciseness contributes to the missing usage and parameter detail.

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?

For a simple two-parameter read-only tool, the annotations carry safety semantics and the description lists returned fields in lieu of an output schema. However, it remains incomplete regarding how rule_ids are used, environment behavior, and what happens when IDs are not found.

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 description coverage is only 50%, with rule_ids lacking any schema description and only env documented. The description mentions no parameters at all, so it does not compensate for the undocumented required rule_ids array or explain accepted ID formats or cardinality.

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 clearly identifies the resource as rule definitions and lists the fields returned (level, description, file, groups, conditions). The retrieve action is implied rather than stated with an explicit verb, and it does not explicitly differentiate itself from siblings such as rule_timeline or simulate_rule.

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 use this tool versus alternatives, nor any stated prerequisites or exclusions. The agent must infer that it is a lookup by rule IDs from the name and schema alone.

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