Skip to main content
Glama

get_request_status

Retrieve the status, progress, and timing of an Ambari request by ID to monitor operations and troubleshoot failures.

Instructions

Retrieves the status and progress of a specific Ambari request operation.

[Tool Role]: Dedicated tool for real-time tracking and reporting of Ambari request status.

[Core Functions]:

  • Query the status, progress, and context of a request by its ID

  • Provide detailed status (PENDING, IN_PROGRESS, COMPLETED, FAILED, etc.)

  • Show progress percentage and timing information

  • Return actionable status for automation and LLM integration

[Required Usage Scenarios]:

  • When users ask for the status or progress of a specific operation/request

  • When monitoring or troubleshooting Ambari operations

  • When tracking bulk or individual service actions

  • When users mention request ID, operation status, or progress

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": {
      "request_id": "<request_id>"
    },
    "name": "get_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesID of the Ambari request to check (int)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.8.2
    • addedInput schema / properties / request_id / description
      Added value: +"ID of the Ambari request to check (int)"
  2. Changed4 schema fields changedv3.7.5
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / request_id / title
      Removed value: -"Request Id"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful traits: it enumerates the possible statuses (PENDING, IN_PROGRESS, COMPLETED, FAILED), states that progress percentage and timing are reported, and frames the call as a read-only real-time lookup. It omits what happens with an unknown/expired request ID and any retention limits on historical requests.

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 opening sentence is well front-loaded, but the bracketed [Tool Role]/[Core Functions]/[Required Usage Scenarios] scaffolding is bulky and partly redundant, and lines like 'Return actionable status for automation and LLM integration' add no information an agent can act on.

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?

For a single-parameter read tool with an output schema already defining return shape, the description covers purpose, when to call, and the status vocabulary. Missing edge-case behavior (invalid/unknown request ID) is a minor gap, not a blocking one.

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% for the single request_id parameter, so the baseline is 3. The description only re-states 'by its ID' and does not clarify the schema's own ambiguity (the property is typed 'string' but described as '(int)'), which is exactly the kind of gap prose could have resolved.

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 names a specific verb and resource: 'Retrieves the status and progress of a specific Ambari request operation.' The 'by its ID' scoping implicitly separates it from get_active_requests (listing) and get_request_tasks (task-level detail), though no sibling is named explicitly.

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 four concrete triggers (user asks for operation status, monitoring/troubleshooting, tracking bulk or individual actions, mention of request ID). This is clear positive guidance, but there is no exclusion or explicit alternative named (e.g., use get_active_requests when no ID is known).

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