Skip to main content
Glama

get_task_status

Read-only

Checks the status of a previously started task using its task_ref, optionally waiting up to 120 seconds for a result before returning a polling reference.

Instructions

Check a task started earlier in this session, by the task_ref it returned. Free. Only refs issued by this server are accepted.

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_ref": "<task_ref>"
    },
    "name": "get_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_refYes
wait_secondsNoSeconds to wait for the result before returning a task_ref to poll. Default 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real value with 'Free' (no cost/quota impact) and the acceptance rule for foreign refs. However it omits the most behaviorally significant trait — that the call can block for up to 120 seconds and may return a ref to poll — leaving that only in the schema's wait_seconds description.

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?

Three short, front-loaded fragments with zero filler: purpose first, then cost, then the acceptance constraint. Nothing repeats the name or title, and every clause carries information the agent would not otherwise have.

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?

For a two-parameter read call with annotations covering safety, the definition is close to sufficient, but with no output schema the agent is never told what a status response looks like or what to do when the task is not finished. The polling/blocking semantics live only in a single parameter description rather than being surfaced in the description itself.

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?

With 50% schema coverage, the description compensates for the undocumented task_ref by explaining its origin (returned by the earlier task) and its validity constraint (only refs issued by this server). The wait_seconds parameter's meaning is carried entirely by the schema, so the description adds nothing there.

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?

States a specific verb+resource: 'Check a task started earlier in this session' and identifies the key by which it is addressed ('by the task_ref it returned'). That is enough for an agent to know this retrieves the state of a previously launched job, though it never says what status information is actually reported.

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?

Gives clear preconditions: the task must have been 'started earlier in this session' and the ref must be one 'issued by this server,' which implicitly rules out foreign task IDs. It does not name alternatives (e.g. how to start a task or how to poll repeatedly), so the when-to-use context is present but not exhaustive.

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