Skip to main content
Glama
Node Mantis

Node Mantis

Official

Check a task

get_task
Read-onlyIdempotent

Retrieves the status, progress and final result of a background task started by run_task or retrieve_data. Waits up to wait_seconds and returns when done or still running.

Instructions

Wait for a task started by run_task or retrieve_data and return its status, latest progress and, once finished, its result. Returns as soon as the task finishes, or after wait_seconds with status "running" (call again). Tasks are kept for an hour after they finish and are lost when this server restarts.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task_id returned by run_task or retrieve_data.
wait_secondsNoHow long to wait for the task to finish before answering. 0 answers immediately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.9

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses important behavior: long-polling semantics, the "running" timeout outcome, retry guidance, one-hour retention, and loss on server restart. These are exactly the operational details an agent needs to avoid misinterpreting a non-final response.

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?

The description is compact and front-loaded, covering the action, timeout behavior, and retention constraints in three efficient sentences. Every sentence carries useful operational information.

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?

For a polling tool with no output schema, the description sufficiently states that it returns status, latest progress, and the final result. It also covers retention and timeout behavior, leaving no major operational gap.

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

Parameters4/5

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

The schema has full parameter coverage, so the baseline is 3. The description still adds meaning by explaining that wait_seconds controls how long the call blocks and that expiry returns "running" with a need to call again.

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 uses a specific verb and resource: it waits for a task created by run_task or retrieve_data and returns status, progress, and result. It clearly distinguishes this polling/checking role from the task-starting 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?

It explicitly says to use this for tasks started by run_task or retrieve_data, and it explains that callers should call again when wait_seconds expires with status "running". It does not contrast cancel_task, but the usage context is otherwise clear.

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