Skip to main content
Glama
wazuh-daily-triage

wazuh-daily-triage

correlate_around

Read-only

Find other alerts within ±N minutes (default 30) of a given timestamp, optionally limited to the same agent, to correlate related security events.

Instructions

Other alerts within ±N minutes (default 30) of a timestamp, optionally on the same agent.

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": {
      "timestamp": "<timestamp>"
    },
    "name": "correlate_around"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNoenvironment id (list_environments)
agentNo
minutesNo
min_levelNo
timestampYes

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds one genuinely behavioral fact beyond them: the ±30 minute default window. It says nothing about result ordering, caps on returned alerts, or how min_level affects the output, which are the traits an agent would still want.

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?

A single front-loaded sentence with the default value inlined parenthetically; no filler and nothing that could be removed without losing meaning.

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

Completeness2/5

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

For a five-parameter, read-only query tool with no output schema and 20% schema coverage, the description is too thin. It omits return shape, ordering/limits, timestamp format, and min_level semantics, leaving an agent guessing on four of five parameters.

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 20%, so the description carries most of the burden, and it only clarifies two of five parameters: minutes (default 30) and agent (optional, must be the same agent). min_level, timestamp (expected format), and env's tie to list_environments are left entirely to the schema.

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 resource (alerts) and a specific scope (within ±N minutes of a timestamp, optionally on the same agent), so an agent can tell it is a temporal-correlation query rather than a generic search. It stops short of distinguishing itself from search_alerts, and the word 'Other' is ambiguous since no alert id is passed, only a timestamp.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named despite search_alerts being a plausible competitor. The only usage hint is the parenthetical 'optionally on the same agent', which implies narrowing but does not state the condition for doing so.

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