Skip to main content
Glama

get_service_components

Retrieve a service's components with state, category, host assignments, and instance counts to troubleshoot health or scaling in an Ambari cluster.

Instructions

Retrieves detailed components information for a specific service in the Ambari cluster.

[Tool Role]: Dedicated tool for retrieving service component details and host assignments.

[Core Functions]:

  • List all components for a service, including state and category

  • Show host assignments and instance counts

  • Provide formatted output for LLM automation and troubleshooting

[Required Usage Scenarios]:

  • When users request service component details or host info

  • When troubleshooting service health or scaling

  • When users mention component list, host assignments, or service breakdown

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_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_nameYesName of the service (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 (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

B3.4/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 burden. It does disclose that output includes component state, category, host assignments and instance counts, which is meaningful behavioral context. It says nothing about permissions, error behavior if the service name is wrong, or cost/latency, and the claim of 'formatted output for LLM automation' is vague.

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 one-sentence purpose is front-loaded and correct, but it is followed by three bracketed sections of largely restated content. '[Core Functions]' repeats host assignments and component listing already implied, and 'Provide formatted output for LLM automation' is filler that doesn't help selection.

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-required-parameter read tool with an output schema that carries the return shape, the description supplies enough: what it returns, when to use it, and the scope of the service argument. Missing only the sibling disambiguation that a crowded toolset like this one would benefit from.

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?

Only one parameter and schema coverage is 100%, with examples ("HDFS", "YARN", "HBASE") already in the schema. The description adds no syntax or naming guidance beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: retrieves component details for a named service in the Ambari cluster, plus host assignments. The '[Tool Role]' line explicitly positions it as the dedicated component-details tool, which partially separates it from siblings like get_service_details and get_service_status, though it never names those siblings directly.

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

Usage Guidelines3/5

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

Lists 'Required Usage Scenarios' (component details, host info, troubleshooting health/scaling), which gives positive triggers. However, it offers no exclusions and no alternatives — an agent cannot tell from this text why it should call this rather than get_service_details or get_service_status.

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