Skip to main content
Glama

Read the current state of a task (read-only, never blocks)

dsh_get_task
Read-onlyIdempotent

Retrieve a non-blocking status snapshot for a delegated task, including its current state, stage summary, liveness, cancel/timeout facts, and whether it can accept another stage.

Instructions

Returns the eight-state task state, the current stage summary, runtime liveness, cancel/timeout facts and whether the task can accept another stage. Never blocks.

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": {
      "taskId": "<taskId>"
    },
    "name": "dsh_get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the bar is lower. The description nonetheless adds real behavioral context by naming the specific facts returned (eight-state model, stage summary, liveness, cancel/timeout facts, stage-acceptance) and reinforcing the non-blocking guarantee, which tells the agent the call is safe to poll frequently.

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?

A single dense sentence with the returned facts front-loaded and the non-blocking guarantee placed last for emphasis. It is efficient, though the compressed enumeration ('eight-state task state', 'runtime liveness') verges on jargon without unpacking.

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?

With no output schema, the description must characterize the return value, and it does list the categories of information returned. It falls short on the taskId parameter, error behavior for unknown or expired task IDs, and what the 'eight-state' enumeration actually contains, which leaves an agent guessing at parsing the response.

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

Parameters2/5

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

The single parameter taskId has 0% schema description coverage, and the description never mentions it, its format, or where it comes from. With one required parameter, the description should carry the burden of explaining the identifier and what happens with an unknown or completed task, and it does not.

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 (returns) and resource (task state) and enumerates the facts returned: state, stage summary, liveness, cancel/timeout facts, and stage acceptance. It implicitly distinguishes itself from dsh_wait_task by saying 'Never blocks', but it never names the result/history siblings it differs from, so differentiation is only partial.

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

Usage Guidelines3/5

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

'Never blocks' implies the polling/inspection use case versus a blocking wait, which is useful implied guidance. However, there is no explicit statement of when to use this versus dsh_get_result, dsh_get_history, or dsh_wait_task, and no prerequisites for the taskId are given.

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