Skip to main content
Glama

Get ZCode task result

zcode_result
Read-only

Fetch a task's final answer text and token usage, or check its running status when no result is ready.

Instructions

Final answer text of a finished task (plus token usage). For a task still running this returns its status without a result.

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

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish a safe read-only, non-open-world operation, and the description adds genuinely new behavior: the response includes token usage, and a non-terminal task yields status without a result. It still doesn't say what happens for an unknown or expired taskId, but the core response-shape behavior is disclosed.

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 with the primary outcome front-loaded and the running-task caveat second. No filler or restatement of the title.

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?

For a single-parameter read tool with no output schema, the description supplies what matters: what is returned, that token usage comes with it, and the non-terminal case. The remaining gap is identifier provenance and error behavior, which is minor at this complexity.

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 description coverage is 0%, so the lone parameter taskId has no documented meaning anywhere. The description refers to 'a task' but never explains that the identifier corresponds to a session-style ID (the schema pattern is '^sess(ion)?_[\w-]+$'), nor where to obtain it, so it only partially compensates for the schema gap.

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?

The description names a specific resource and outcome: the final answer text of a finished task, plus token usage. That clearly separates it from status/wait/cancel-type siblings, though it never explicitly distinguishes it from zcode_structured_result, which serves a similar retrieval role.

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?

It implies the tool is for finished tasks and warns that a still-running task returns only status. However, it never states when to prefer this over zcode_status, zcode_wait, or zcode_structured_result, leaving the agent to infer the routing from sibling names alone.

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