Skip to main content
Glama

List recent ZCode tasks

zcode_list
Read-only

Lists recent non-archived subagent project tasks with their status and optional result limit, so you can review active work and track progress.

Instructions

Recent (non-archived) tasks in the subagent project with their status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zcode_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful filtering facts — archived tasks excluded, scope confined to the subagent project — but says nothing about ordering, default window size, or how many items come back when limit is omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, but it is a noun phrase rather than a complete statement, so the core action is absent from the front of the definition. Brevity here comes partly at the cost of clarity.

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 simple read-only list tool with annotations covering the safety profile and no output schema, the essentials are close to covered. Still missing are the default/maximum result behavior and result ordering, which an agent needs to page or reason about recency.

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?

One optional parameter, limit (1–50), has 0% schema description coverage, and the description never mentions it. The word 'recent' hints at a default recency window but gives no hint about how the limit interacts with that window or what the default is.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment identifies the resource (tasks) and two scoping traits — 'recent (non-archived)' and 'subagent project' — which do separate it from archival or cross-project listings. However, there is no verb; the reader must infer 'lists' from the title. Purpose is recognizable but not stated as an action.

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

Usage Guidelines2/5

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

No when-to-use guidance and no named alternatives. With siblings like zcode_status, zcode_progress, and zcode_result that plausibly overlap in reporting task state, the description never says why an agent should pick this listing over those.

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