MCP-Ambari-API

by call518

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Query Ambari Metrics

query_ambari_metrics

Fetch specific time-series metrics from Ambari Metrics to monitor Hadoop cluster performance and resource usage.

Instructions

Fetch time-series metrics (exact metric names only) from Ambari Metrics.

Input Schema

TableJSON Schema

Name	Required	Default
`metric_names`	Yes
`app_id`	No
`hostnames`	No
`duration`	No	1h
`start_time`	No
`end_time`	No
`precision`	No
`temporal_aggregator`	No
`temporal_granularity`	No
`group_by_host`	No
`include_points`	No
`max_points`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv3.7.5May 14, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties / app_id / title
```
Removed value: -"App Id"
```
- removedInput schema / properties / duration / title
```
Removed value: -"Duration"
```
- removedInput schema / properties / end_time / title
```
Removed value: -"End Time"
```
- removedInput schema / properties / group_by_host / title
```
Removed value: -"Group By Host"
```
- removedInput schema / properties / hostnames / title
```
Removed value: -"Hostnames"
```
- removedInput schema / properties / include_points / title
```
Removed value: -"Include Points"
```
- removedInput schema / properties / max_points / title
```
Removed value: -"Max Points"
```
- removedInput schema / properties / metric_names / title
```
Removed value: -"Metric Names"
```
- removedInput schema / properties / precision / title
```
Removed value: -"Precision"
```
- removedInput schema / properties / start_time / title
```
Removed value: -"Start Time"
```
- removedInput schema / properties / temporal_aggregator / title
```
Removed value: -"Temporal Aggregator"
```
- removedInput schema / properties / temporal_granularity / title
```
Removed value: -"Temporal Granularity"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"_WrappedResult"
```
Addedv1.0.0Jan 3, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It only mentions the constraint 'exact metric names only' but does not address data volume limits, rate limiting, authentication requirements, or other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise but overly brief. It front-loads the action but lacks necessary detail. Given the tool's complexity, the sentence is too short to be effective.

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?

Despite the presence of an output schema, the description fails to provide context for the numerous parameters or the exact nature of the returned metrics. It covers only the basic purpose, leaving many aspects unexplained.

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

Parameters1/5

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

With 0% schema description coverage and 12 parameters (including optional ones like app_id, hostnames, duration), the description does not explain any parameter. The agent must infer parameter usage from names alone, which is insufficient.

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 explicitly states 'Fetch time-series metrics (exact metric names only) from Ambari Metrics,' which clearly identifies the verb (fetch), resource (time-series metrics), and constraint (exact metric names). It distinguishes itself from sibling tools like 'list_ambari_metrics_metadata' and 'list_ambari_metric_apps'.

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 is provided on when to use this tool versus alternatives, such as listing metrics first or using other query tools. The description simply states what it does without contextual usage advice.

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