Skip to main content
Glama

stop_host_component

Stops a specified component on a single Ambari host, enabling targeted shutdown without affecting other hosts or services. Use it for node-level troubleshooting, isolation, or decommissioning.

Instructions

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

[Tool Role]: Dedicated tool for stopping 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

  • Skip if the component is already in INSTALLED (stopped) state

  • Return request information for progress tracking

[Required Usage Scenarios]:

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

  • When decommissioning or isolating a specific node's component

  • When troubleshooting a single component instance

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

Input Schema

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

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

With no annotations, the description carries the full burden and does add real behavioral context: the call is a no-op if the component is already INSTALLED, and it returns request information for progress tracking. It omits any warning about service disruption or required permissions, which is notable for a stop operation.

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?

Front-loaded with a one-sentence purpose, then structured under bracketed headers that make scanning easy. The header scaffolding ('[Core Functions]', '[Required Usage Scenarios]') is slightly heavier than needed, but no sentence is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still points the agent to request-based progress tracking. For a two-parameter host-level operation, everything needed to select and invoke it correctly is present.

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% with two required parameters, both documented with formats and examples in the schema itself. The description adds nothing about parameter syntax or constraints beyond what the schema already provides, so the 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 (stops) and resource (a specific component on a specific host), then scopes it explicitly as host-level rather than service-level. The line 'without affecting other hosts or the overall service' distinguishes it from the sibling stop_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?

Provides three concrete usage scenarios with a quoted example ('stop DataNode on host-A') and covers decommissioning/isolation and troubleshooting cases. It implies but never explicitly states the counterpart boundary (use stop_service for a whole service), so exclusions are left to inference.

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