Skip to main content
Glama

stop_service

Stops a specified Ambari cluster service and returns request details for shutdown progress tracking, supporting maintenance and troubleshooting automation.

Instructions

Stops a specific service in the Ambari cluster.

[Tool Role]: Dedicated tool for automated stop of Ambari services, ensuring safe and monitored shutdown.

[Core Functions]:

  • Stop the specified service and initiate Ambari request

  • Return request information for progress tracking

  • Provide clear success or error message for LLM automation

[Required Usage Scenarios]:

  • When users request to "stop" a service (e.g., "stop HDFS", "stop YARN")

  • When maintenance or troubleshooting requires a service shutdown

  • When users mention service stop, shutdown, or automated stop

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

Input Schema

NameRequiredDescriptionDefault
service_nameYesName of the service to stop (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 stop (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.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden for a destructive operation. It does add genuinely useful behavior: the stop is asynchronous and returns request information for progress tracking (implying get_request_status follow-up). But it omits permission requirements, irreversibility, what happens to running components, and behavior when the service is already stopped.

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 core sentence is correctly front-loaded, but the bracketed sections repeat the same idea three times ('stop', 'shutdown', 'automated stop') and lines like 'Provide clear success or error message for LLM automation' are meta-filler about the tool's own design rather than information an agent can act on.

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

Completeness3/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 single parameter is fully documented. For a mutation tool with zero annotations, however, the description should still say whether the stop is graceful, blocking, or affects dependent components.

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 exists and schema coverage is 100%, with the schema already supplying examples ('HDFS', 'YARN', 'HBASE'). The description adds nothing about case sensitivity or valid name sources, 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?

The description opens with a specific verb and resource ('Stops a specific service in the Ambari cluster'), and the word 'specific' implicitly distinguishes it from stop_all_services and stop_host_component. It never names those siblings explicitly, so the differentiation is left partly to inference.

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]' block gives concrete trigger phrases ('stop HDFS', 'stop YARN') and conditions (maintenance, troubleshooting, shutdown requests), which is more than most tools offer. It stops short of naming the alternatives (stop_all_services, stop_host_component) or stating when this tool should not be used.

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