Skip to main content
Glama

start_service

Starts a specified Ambari service and returns request details for progress tracking, enabling safe automated recovery or maintenance startup.

Instructions

Starts a specific service in the Ambari cluster.

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

[Core Functions]:

  • Start 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 "start" a service (e.g., "start HDFS", "start YARN")

  • When recovering stopped services

  • When maintenance or configuration changes require a service start

  • When users mention service start, bring up service, or automated start

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

Input Schema

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

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

No annotations exist, so the description carries the full burden. It usefully discloses that the tool initiates an Ambari request and returns request info for progress tracking plus a success/error message, which tells the agent this is asynchronous. It does not cover idempotency (behavior if the service is already running), required permissions, or how errors surface — meaningful gaps for a mutation tool.

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 bracketed [Tool Role]/[Core Functions]/[Required Usage Scenarios] scaffolding is boilerplate that inflates length, and the final bullet ('service start, bring up service, or automated start') restates earlier scenarios. The core purpose is still front-loaded in the first sentence, so it is usable but not tight.

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-value explanation is not required, and the description covers trigger conditions plus the async-request nature of the call. Minor gaps around permissions and already-running services, but for a one-parameter tool this is close to sufficient.

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% with a single required parameter already documented with example values, so the schema does the heavy lifting. The description adds only loose reinforcement via example service names ('start HDFS', 'start YARN') and no syntax or case-sensitivity guidance beyond the schema.

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 (starts) and resource (a specific service in the Ambari cluster), and the word 'specific' plus the singular 'service' implicitly separates it from start_all_services and start_host_component. However, the description never names those siblings explicitly, leaving the agent to infer the boundary.

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 a concrete list of triggering scenarios ('start HDFS', recovering stopped services, after config changes, synonyms like 'bring up'). Clear context for invocation, but no explicit exclusions or named alternatives such as start_all_services or restart_service for already-running services.

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