Skip to main content
Glama

start_host_component

Start one Ambari component on a specific host to recover a stopped instance without restarting its service or affecting other hosts. Skips already-started components; returns request details.

Instructions

Starts a specific component on a specific host in the Ambari cluster.

[Tool Role]: Dedicated tool for starting individual host-level components, enabling fine-grained control without affecting other hosts or the overall service.

[Core Functions]:

  • Start the specified component on the given host

  • Skip if the component is already in STARTED state

  • Return request information for progress tracking

[Required Usage Scenarios]:

  • When a specific host's component is STOPPED but the overall service is STARTED

  • When users request to start a component on a specific host (e.g., "start DataNode on host-A")

  • When recovering a single component instance without restarting the entire service

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": {
      "host_name": "<host_name>",
      "component_name": "<component_name>"
    },
    "name": "start_host_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_nameYesHostname where the component resides (e.g., "hdp-node-01.example.com")
component_nameYesName of the component to start (e.g., "DATANODE", "NODEMANAGER")

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.8.2
    • addedInput schema / properties / component_name / description
      Added value: +"Name of the component to start (e.g., \"DATANODE\", \"NODEMANAGER\")"
    • addedInput schema / properties / host_name / description
      Added value: +"Hostname where the component resides (e.g., \"hdp-node-01.example.com\")"
  2. Addedv3.7.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden and does well: it states that the component starts on the given host, that it skips already-STARTED components, and that it returns request information for progress tracking. It does not cover permissions, failure behavior, or side effects beyond the start action, which keeps it from a 5.

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 first sentence is front-loaded and the sectioned structure makes the tool's role, functions, and scenarios easy to scan. It is somewhat verbose and repetitive, especially around 'specific host/component', but not enough to obscure the content.

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?

The description is complete enough for an agent to identify when to call this tool and what it does, while the input schema fully documents both required parameters and an output schema exists for return values. The main remaining gap is the absence of permission or prerequisite guidance for a mutating start operation.

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 description coverage is 100%, so the baseline is 3. The description reinforces that the action targets a specific host and component but adds no syntax, constraints, or format details beyond what the input schema already provides.

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 states a specific verb and resource: starting a specific component on a specific host in Ambari. It clearly distinguishes this host-level action from service-level operations by emphasizing fine-grained control without affecting other hosts or the overall service.

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 description gives explicit usage scenarios, including when a component is STOPPED while the service is STARTED, when a user asks to start a component on a host, and when recovering a single instance without restarting the service. It does not explicitly name sibling alternatives such as start_service or restart_host_component, so it stops short of full when-not/alternative guidance.

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