Skip to main content
Glama
Sign In
mcp-server-wazuh

mcp-server-wazuh

by VitexSoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Cluster Nodes

list_cluster_nodes
Read-onlyIdempotent

Retrieve all Wazuh cluster nodes to check membership, roles, and status for cluster monitoring and troubleshooting.

Instructions

List Wazuh cluster nodes.

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_cluster_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no mention of whether the list is cluster-wide or node-local, whether results can be empty, or how the call behaves when the cluster is down.

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?

A single front-loaded sentence with no filler, boilerplate, or redundancy. It is as short as it can be, though that brevity is also the source of its informational gaps rather than a structural flaw.

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?

The tool is simple (no parameters, read-only, and an output schema exists that explains return values), so the description is not required to explain much. Still, one clause about what a 'node' is in this cluster context, or how it relates to get_cluster_status, would make it complete rather than merely adequate.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The empty schema with additionalProperties=false is fully self-explanatory.

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 uses an explicit verb (List) and a specific resource (Wazuh cluster nodes), so an agent knows exactly what it retrieves. It does not distinguish itself from near-neighbours such as get_cluster_status or list_agents, leaving the sibling boundary to be inferred from the names alone.

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 when-to-use guidance, no stated prerequisites, and no mention of the alternative get_cluster_status tool for cluster-related questions. The only usage signal is the verb 'List', which the agent could already derive from the tool name.

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