Skip to main content
Glama

get_host_details

Retrieve detailed information for a specific Ambari host or all cluster hosts, including hardware specs, state, metrics, and assigned components for monitoring and troubleshooting.

Instructions

Retrieves detailed information for a specific host or all hosts in the Ambari cluster.

[Tool Role]: Dedicated tool for retrieving comprehensive host details including metrics, hardware info, and components.

[Core Functions]:

  • If host_name provided: Query specific host information

  • If host_name not provided: Query all hosts and their detailed information

  • Return host hardware specs, state, metrics, and assigned components

  • Provide formatted output for LLM automation and cluster management

[Required Usage Scenarios]:

  • When users request specific host details or host status

  • When users request all hosts details or cluster-wide host information

  • When auditing or monitoring individual or all cluster nodes

  • When troubleshooting host-specific issues

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": "get_host_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_nameNoName of the specific host to retrieve details for (optional, e.g., "bigtop-hostname0.demo.local")

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.8.2
    • addedInput schema / properties / host_name / description
      Added value: +"Name of the specific host to retrieve details for (optional, e.g., \"bigtop-hostname0.demo.local\")"
  2. Changed4 schema fields changedv3.7.5
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / host_name / title
      Removed value: -"Host Name"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose that it returns hardware specs, state, metrics and assigned components, and that omitting host_name fans out to every host in the cluster. The notable gaps are that it never mentions cost/volume implications of the all-hosts mode or any pagination or failure behavior for an unknown host name.

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 header/bullet scaffolding front-loads purpose well, but there is padding: '[Tool Role]' restates the first sentence, and 'Provide formatted output for LLM automation' is filler that tells an agent nothing actionable. Roughly half the text is load-bearing.

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 single optional-parameter read tool with an output schema, the description covers scope, dual mode, and returned data, which is nearly everything an agent needs. The remaining omission is the relationship to sibling host tools (list_hosts, get_service_components), which would prevent ambiguous tool selection.

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%, so host_name is already documented with an example value, giving a baseline of 3. The description does add one genuinely new piece of semantics — that omitting the parameter returns all hosts — but it adds nothing about name format or matching rules beyond the schema example.

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?

Opens with a specific verb+resource ('Retrieves detailed information for a specific host or all hosts') and names the cluster scope, which is clearer than the title alone. It doesn't distinguish itself from the nearby 'list_hosts' sibling, so an agent can't tell from the description alone which one gives summaries vs. deep detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The '[Required Usage Scenarios]' block gives concrete triggers: host status requests, cluster-wide host info, auditing/monitoring, and troubleshooting. That is clear positive guidance, but there are no exclusions or named alternatives (e.g., use list_hosts for a cheap inventory), so it stops short of full when-vs-what guidance.

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