Skip to main content
Glama
Sign In
agent-pool-mcp

agent-pool-mcp

by rnd-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_task_result

Retrieve the status and result of a background task using its task ID. Completed results are available until TTL cleanup.

Instructions

Check the status and result of a background task started with delegate_task, delegate_task_readonly, or consult_peer. Completed results remain available until TTL cleanup, so multiple callers can retrieve the full report.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID returned by delegate_task, delegate_task_readonly, or consult_peer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.3

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that results persist until TTL cleanup and that multiple callers can retrieve the full report. It does not discuss error handling or auth requirements, but the disclosed persistence and multi-caller support are valuable behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the primary action, no redundant wording. Every sentence adds value.

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?

Given no output schema, the description would benefit from describing the report format or response structure. It covers usage and result persistence adequately but omits details about what the 'full report' contains. Completeness is moderate.

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%, and the description does not add meaning beyond the schema's description of task_id. The baseline of 3 is appropriate as the schema already documents the parameter sufficiently.

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 verb 'check' and the resource 'status and result of a background task', and distinguishes it by specifying the initiating tools (delegate_task, delegate_task_readonly, consult_peer). This differentiates it from sibling tools like cancel_task or get_pipeline_status.

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 clear context that this tool is used after starting a background task with specific delegating tools. However, it does not explicitly state when not to use it or contrast with alternatives like cancel_task. The guidance is clear but lacks exclusion criteria.

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

Deploy Server

Other Tools