Skip to main content
Glama

get_request_tasks

Retrieve host-by-host task details for an Ambari request and filter by status or hostname to identify failed, pending, or running roles.

Instructions

Retrieves task-level details for a specific Ambari request (host-by-host breakdown).

[Tool Role]: Provides granular, per-host task information for an Ambari request, going beyond the summary level offered by get_request_status.

[Core Functions]:

  • List all tasks (host/role/status/timing) belonging to a request

  • Filter tasks by status (e.g. FAILED, IN_PROGRESS) or exclude a status (not:COMPLETED)

  • Filter tasks by hostname to inspect a specific host

  • Identify which hosts/roles are failing, pending, or still running

[Required Usage Scenarios]:

  • When users want to know which hosts or roles failed/are pending in an operation

  • When debugging a partially-failed bulk operation (e.g. "Start all services")

  • When users ask for task details, host-level progress, or remaining tasks

  • When request progress is near 100% but not complete and user wants to know what's left

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_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesID of the Ambari request to inspect (integer string)
host_filterNoOptional hostname substring to restrict results to matching hosts.
status_filterNoOptional status to filter on. Use exact status names (PENDING, IN_PROGRESS, COMPLETED, FAILED, ABORTED, TIMEDOUT) or prefix with "not:" to exclude that status (e.g. "not:COMPLETED" shows only unfinished tasks).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.8.2
    • addedInput schema / properties / host_filter / description
      Added value: +"Optional hostname substring to restrict results to matching hosts."
    • addedInput schema / properties / request_id / description
      Added value: +"ID of the Ambari request to inspect (integer string)"
    • addedInput schema / properties / status_filter / description
      Added value: +"Optional status to filter on. Use exact status names (PENDING,\nIN_PROGRESS, COMPLETED, FAILED, ABORTED, TIMEDOUT) or prefix with \"not:\"\nto exclude that status (e.g. \"not:COMPLETED\" shows only unfinished tasks)."
  2. Addedv3.7.5

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. The retrieval/list wording makes the read-only nature clear, and the filtering behavior is described, but it does not mention permissions, error behavior, pagination, or other operational traits. The output schema reduces the need to explain return values, but the behavioral disclosure is only adequate.

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?

The definition is front-loaded with a clear one-sentence purpose and uses headings and bullets that make it easy to scan. It is somewhat repetitive between the opening sentence, Tool Role, and Core Functions, but the extra structure remains useful rather than wasteful.

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 three-parameter read tool with full schema description coverage and an output schema, the description is complete enough to call correctly. It explains the tool's scope, filters, and alternatives, though it could say more about prerequisites or failure behavior for a fully self-contained definition.

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%, so the baseline is 3. The description reinforces hostname and status filtering and gives examples such as FAILED, IN_PROGRESS, and not:COMPLETED, but these are already documented in the schema and it does not add new syntax or constraints beyond that.

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?

The description opens with a specific verb and resource: retrieving task-level details for a specific Ambari request, with host-by-host breakdown. It also explicitly distinguishes the tool from get_request_status by saying it goes beyond summary-level information. An agent can identify what this tool returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names concrete scenarios for use: identifying failed or pending hosts, debugging partially failed bulk operations, asking for task details, and inspecting what remains when progress is near 100%. It also positions get_request_status as the summary-level alternative, making the selection condition explicit.

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