Skip to main content
Glama

get_group_agents

Retrieve all agents assigned to a specific Wazuh group, with optional pagination and IP inclusion.

Instructions

List agents belonging to a specific Wazuh group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup name/identifier (e.g., 'default', 'linux-servers')
limitNoMaximum number of items to return (1-100)
offsetNoPagination offset
include_ipNoInclude agent IP addresses in the response
Behavior2/5

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

No annotations provided, yet the description fails to disclose behavioral traits such as pagination (limit/offset), agent status filtering, or error handling for invalid group_id.

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?

Extremely concise single sentence, front-loaded with purpose. No wasted words, but could benefit from a bit more structure or detail.

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?

Lacks context on return format, pagination behavior, ordering, and error cases. Since no output schema exists, description should hint at the structure of the returned list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for all parameters. The description adds no additional meaning beyond what the schema already provides.

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 states the tool lists agents for a specific group, but doesn't differentiate from sibling tools like 'list_agents' which also lists agents.

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?

No guidance on when to use this tool versus alternatives (e.g., list_agents with filters). No context on prerequisites or typical usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lidless-labs/wazuh-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server