Skip to main content
Glama

get_request_tasks

Retrieve per-host task details for an Ambari request to identify failed, pending, or running tasks. Filter by status or host to debug partial failures and track remaining work.

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

Args: request_id: ID of the Ambari request to inspect (integer string) status_filter: Optional 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). host_filter: Optional hostname substring to restrict results to matching hosts.

Returns: Task list formatted as a table (success) or an error message (failure). - Success: header with request summary + per-task rows (task_id, host, role, status, duration) - Failure: English error message describing the problem

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idYes
status_filterNo
host_filterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description details the behavior: listing tasks with filtering capabilities and return format. However, it does not explicitly state that the tool is read-only or mention authentication needs. Since annotations are absent, the description carries full burden but is still thorough.

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 description is well-structured with sections and front-loaded purpose. However, it is fairly long; while every sentence is useful, slight trimming could improve conciseness without losing value.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple filters, use cases), the description covers all necessary aspects: parameters, return format (table vs error), and usage scenarios. No output schema is needed as the description explains the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter: request_id as integer string, status_filter with exact statuses and 'not:' prefix logic, host_filter as substring. This adds critical meaning beyond the bare schema.

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 clearly states the tool retrieves task-level details for a specific Ambari request with a host-by-host breakdown, and it explicitly differentiates from the sibling tool 'get_request_status' which provides summary-level data.

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?

The 'Required Usage Scenarios' section explicitly lists when to use this tool, such as debugging partially-failed operations or when request progress is near 100% but incomplete. It provides clear context for use vs. alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/call518/MCP-Ambari-API'

If you have feedback or need assistance with the MCP directory API, please join our Discord server