Skip to main content
Glama
Sign In
Ambari MCP Server

Ambari MCP Server

by nikita15p
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ambari_alerts_addnotificationtogroup

Adds a notification target to an alert group in Ambari to ensure alerts trigger the specified notification.

Instructions

Add a notification target to an alert group

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clusterName": "<clusterName>",
      "groupId": "<groupId>",
      "targetId": "<targetId>"
    },
    "name": "ambari_alerts_addnotificationtogroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterNameYesThe name of the cluster
groupIdYesThe alert group ID
targetIdYesThe notification target ID

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?

No annotations are provided, so the description carries the full burden. It only states the action without disclosing behavioral traits such as whether the operation is idempotent, requires existing objects, or has side effects.

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 description is a single, concise sentence without unnecessary words. However, it could be more informative by including context, so it does not achieve a perfect score.

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 3 required parameters and no output schema, the description is minimally informative. It does not explain the relationship between parameters or any constraints, making it incomplete for effective use in a complex ecosystem.

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 each parameter (clusterName, groupId, targetId) has a straightforward description. The description adds no additional semantic meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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?

The description 'Add a notification target to an alert group' clearly states the specific action (add) and the resources involved (notification target to alert group). It distinguishes from sibling tools like 'ambari_alerts_removenotificationfromgroup' and 'ambari_alerts_createnotification'.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'ambari_alerts_removenotificationfromgroup' or 'ambari_alerts_duplicatealertgroup'. No prerequisites, exclusions, or context for appropriate use are mentioned.

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