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

wazuh-daily-triage

by dururustem68
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_environments

Read-only

Lists available Wazuh environments with IDs, names, and configured extra sources so you can select the correct environment before running triage queries.

Instructions

Environments this server knows (id, name, which extra sources are configured). Call this first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

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 the safety profile is covered. The description adds useful context beyond them: the exact fields returned (id, name, extra-source configuration) despite there being no output schema, plus the prerequisite-sequencing cue. It does not discuss empty results or error behavior, keeping it at a 4.

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 short sentences with the resource and return fields front-loaded and the sequencing cue last; nothing is padding. Slightly telegraphic phrasing ('Environments this server knows') rather than a clean verb-led sentence keeps it from a 5.

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?

With no parameters and no output schema, the description carries the return-shape burden and does so by listing the key fields, plus the 'call first' workflow hint. Enough for correct invocation; only edge cases (empty environment list, auth needs) are unaddressed.

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?

The tool takes zero parameters, so the schema baseline is 4 and there is nothing for the description to disambiguate. No parameter meaning is missing.

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 ('Environments this server knows') and enumerates the returned fields (id, name, configured extra sources), so an agent knows exactly what the tool yields. It is a verb-less fragment rather than an explicit 'list', and no sibling overlaps on this resource, so no differentiation is needed.

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?

'Call this first' gives an explicit ordering instruction that tells the agent when in a sequence to invoke the tool. It stops short of naming alternatives or exclusions, but none of the sibling tools obviously covers environments, so the gap is minor.

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