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

wazuh-daily-triage

by dururustem68
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

knowledge

Read-only

Retrieve and filter baseline, decision, and open-item records for Wazuh daily triage.

Instructions

Knowledge base entries (baseline, decisions, open items...).

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

Input Schema

NameRequiredDescriptionDefault
envNoenvironment id (list_environments)
kindsNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context such as filtering semantics, default environment behavior, pagination, or what the returned entries look like beyond the parenthetical examples.

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 definition is a single short sentence with no wasted wording and is front-loaded. Its brevity is efficient, though it sacrifices clarity and completeness.

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 tool with three parameters, limited schema documentation, and no output schema, the description is too sparse. It does not explain the purpose of the parameters, what a typical result contains, or how this read operation relates to the propose_knowledge mutation sibling.

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 33%, so the description should compensate for undocumented parameters. It does not explain env, kinds, or status, beyond loosely hinting at entry kinds via 'baseline, decisions, open items'—insufficient given the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as knowledge base entries and gives examples of entry kinds (baseline, decisions, open items). However, it provides no verb or scope for the operation—whether it lists, searches, or retrieves—and does not distinguish this tool from the sibling propose_knowledge.

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, no mention of prerequisites, and no exclusions. The only implicit usage signal is the resource name itself.

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