Skip to main content
Glama

get_service_status

Check the current status and state of a specific Ambari cluster service via REST API to monitor service health and troubleshoot issues.

Instructions

Retrieves the status information for a specific service in an Ambari cluster.

[Tool Role]: Dedicated tool for real-time retrieval of specific service status and state information

[Core Functions]:

  • Retrieve specific service status via Ambari REST API

  • Provide detailed service state information (STARTED, STOPPED, INSTALLING, etc.)

  • Include service configuration and component information

[Required Usage Scenarios]:

  • When users ask about specific service status (e.g., "HDFS status", "YARN state")

  • When troubleshooting service issues

  • When monitoring specific service health

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

Input Schema

NameRequiredDescriptionDefault
service_nameYesName of the service to check (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 check (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?

No annotations are provided, so the description carries the burden. It discloses the data source (Ambari REST API) and enumerates possible state values (STARTED, STOPPED, INSTALLING), which is useful, but it never states the operation is read-only, what permissions the caller needs, how failures surface for an unknown service name, or whether the call is expensive.

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 lead sentence is well front-loaded, but the bracketed section headers pad the text and repeat content: '[Tool Role]' restates the opening sentence almost verbatim, and 'Include service configuration and component information' adds length without precision.

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 documented, and the single required parameter is fully covered. What's missing is the differentiating context an agent needs to choose this over get_service_details or get_service_components, plus any note on read-only safety — leaving a regression-tool definition only adequate.

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% for the single service_name parameter, including its own examples, so the schema already does the work. The description adds only that the name identifies a 'specific service' — no case-sensitivity rules or naming conventions beyond what the schema shows.

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 first sentence states a specific verb and resource: retrieve status information for a specific service in an Ambari cluster. It is reasonably distinguishable from get_service_details and get_service_components by emphasizing status/state, though the '[Core Functions]' line 'Include service configuration and component information' blurs the boundary with those 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?

The '[Required Usage Scenarios]' block gives three concrete triggering conditions (user asks about HDFS status, troubleshooting, monitoring health), which is clear context for when to call it. It stops short of a 5 because it names no alternatives or exclusions — an agent is not told to prefer get_service_details when full configuration is needed.

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