Skip to main content
Glama

get_service_details

Retrieve detailed status, component list, and configuration availability for a specific Ambari service to troubleshoot health issues and audit service setup.

Instructions

Retrieves detailed status and configuration information for a specific service in the Ambari cluster.

[Tool Role]: Dedicated tool for retrieving comprehensive service details, including state, components, and configuration.

[Core Functions]:

  • Retrieve service state, component list, and configuration availability

  • Provide formatted output for LLM automation and troubleshooting

[Required Usage Scenarios]:

  • When users request detailed service info or breakdown

  • When troubleshooting service health or auditing service setup

  • When users mention service details, service summary, or configuration status

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": {
      "service_name": "<service_name>"
    },
    "name": "get_service_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_nameYesName of the service to check (e.g., "HDFS", "YARN", "HBASE")

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.8.2
    • addedInput schema / properties / service_name / description
      Added value: +"Name of the service to check (e.g., \"HDFS\", \"YARN\", \"HBASE\")"
  2. Changed4 schema fields changedv3.7.5
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / service_name / title
      Removed value: -"Service Name"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieves' implies a read-only operation and the tool is framed for troubleshooting, but the description does not explicitly confirm read-only behavior, permissions, rate limits, or side effects. With an output schema present, the lack of return-value detail is less serious, but safety/behavioral context is only minimally implied.

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 first sentence is front-loaded and useful, but the bracketed sections repeat the same idea across Tool Role, Core Functions, and Required Usage Scenarios. For a simple one-parameter read tool, the description is longer and more formatted than necessary.

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?

Given a simple one-parameter read tool with an output schema, the description sufficiently explains what is retrieved, including state, components, and configuration availability, and when to use it. The main remaining gap is sibling differentiation against get_service_status and get_service_components, which would help 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?

There is one required parameter and schema description coverage is 100%, so the schema already documents service_name with examples. The description notes that the service is specified, but adds no syntax or constraints beyond the schema, making the baseline score appropriate.

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 first sentence states a specific verb and resource: retrieves detailed status and configuration for a specific service. It is clear what the tool does, but it does not distinguish itself from closely related siblings such as get_service_status, get_service_components, and dump_configurations.

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 section gives clear situations for use: detailed service info, troubleshooting health, auditing setup, and configuration status. It does not specify when to prefer this tool over sibling status/component/configuration tools, so alternatives are not addressed.

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