Skip to main content
Glama

Get ZCode task status

zcode_status
Read-only

Check a task's current state (running, completed, failed, cancelled) without blocking, including elapsed time, active tool, call count and stall detection. Use it for progress; fetch results separately.

Instructions

Non-blocking status of a task: running | completed | failed | cancelled | starting. While running it includes elapsedSec, the tool currently executing, tool call count and idleSec (seconds since the last activity; stalled: true if suspiciously long). Does not include the answer — use zcode_result or zcode_wait for that.

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

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds substantial value on top: the status field set (elapsedSec, current tool, tool call count, idleSec) and the `stalled` heuristic. It stops short of describing persistence of terminal states or polling cost, but discloses more than most status tools.

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 tightly written sentences, front-loaded with the purpose and states, followed by the return-shape detail and the routing exclusion. No filler.

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

Completeness4/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 correctly takes on the burden of describing the return payload, including the running-state fields. The only meaningful gap is the unmentioned taskId semantics, which leaves the one input underspecified.

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?

Schema coverage is 0% and the single parameter taskId is never mentioned in the description, so the agent gets no hint that it expects a session-style identifier matching ^sess(ion)?_[\w-]+$. The description adds no 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?

States a specific verb and resource ('Non-blocking status of a task') and enumerates the exact result states. It also explicitly says what it does not return, distinguishing it from zcode_result and zcode_wait without requiring schema inspection.

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?

Clear usage context: use this for lightweight, non-blocking polling, and use zcode_result or zcode_wait when the actual answer is needed. The exclusion is explicit, though it does not state whether polling frequency matters or when the status becomes final.

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