Skip to main content
Glama

restart_host_component

Restarts a specific component on a given host by stopping then starting it, enabling targeted recovery or config changes without affecting other hosts.

Instructions

Restarts a specific component on a specific host in the Ambari cluster (stop then start).

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

[Core Functions]:

  • Stop the specified component on the given host and wait for completion

  • Start the component and return request information

  • Return clear success or error message for LLM automation

[Required Usage Scenarios]:

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

  • When recovering a stuck or malfunctioning single component instance

  • When applying config changes that require a component-level restart

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

Input Schema

NameRequiredDescriptionDefault
host_nameYesHostname where the component resides (e.g., "hdp-node-01.example.com")
component_nameYesName of the component to restart (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 restart (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

A3.9/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight: it discloses the two-phase stop-then-start sequence, that it waits for stop completion, and that it returns request information plus success/error messaging. However, it omits the operational consequences an agent should know before calling a disruptive operation — expected downtime, whether the start phase is asynchronous (requiring get_request_status polling), and permission prerequisites.

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?

Purpose is front-loaded in the first sentence before the bracketed sections, and the scenario list is scannable. Some filler remains — 'Return clear success or error message for LLM automation' and the '[Core Functions]' framing repeat what the opener already said.

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?

An output schema exists, so return values need not be explained, and the description covers sequencing, scope, and call triggers adequately. The gap is impact disclosure — for a restart with no annotations, saying the component will be briefly unavailable would round it out.

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% and both parameters are documented in-schema with concrete examples (hostname format, 'DATANODE'/'NODEMANAGER'). The description adds only a generic usage example that duplicates what the schema already provides, so baseline 3 applies.

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?

States a specific verb+resource+scope: restarting a single component on a single host, with the mechanics spelled out ('stop then start'). This clearly separates it from restart_service, start_host_component, and stop_host_component among the siblings.

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?

A dedicated 'Required Usage Scenarios' section gives three concrete triggers, including an example utterance ('restart DataNode on host-A'). It implies the alternative (whole-service restart) via 'without affecting other hosts or the overall service' but never names restart_service explicitly as the fallback for service-wide restarts.

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