Skip to main content
Glama
nikita15p

Ambari MCP Server

by nikita15p

ambari_alerts_getalertgroups

Retrieve all alert groups for a specific Ambari cluster to monitor grouping and status.

Instructions

Get all alert groups for a cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clusterNameYesThe name of the cluster
Behavior2/5

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

No annotations provided. Description lacks behavioral details such as read-only nature, pagination, authentication requirements, or any side effects. It doesn't confirm it's a safe read operation.

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?

Single sentence, no extraneous words. Purpose is clear and front-loaded.

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?

For a simple list operation with one parameter and no output schema, the description is adequate. It lacks details on return format but is sufficient for basic understanding.

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% and schema already describes 'clusterName' as 'The name of the cluster'. Description does not add additional meaning or context beyond the schema, meeting baseline.

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

Purpose5/5

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

Description clearly states verb 'Get', resource 'alert groups', and scope 'for a cluster'. It is specific and distinguishes from sibling tools like create, delete, update alert groups.

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. For example, it doesn't mention that this is for listing all groups without filtering, or when to use other alert group tools.

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/nikita15p/ambari-mcp-server'

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