Skip to main content
Glama

List recent swarm tasks across backends

swarm_list
Read-only

List recent tasks from CodeBuddy, Qoder, or ZCode subagent backends, or view all merged newest-first, to audit activity and check job status across the swarm.

Instructions

List recent tasks from CodeBuddy, Qoder, ZCode, or all merged newest-first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
backendNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/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 the safety profile is covered. The description adds real behavioral value with "merged newest-first", which tells the agent how results from multiple backends are combined and ordered, but it says nothing about default limits, truncation, or what a "recent task" entry contains.

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?

One short sentence, zero filler, with the resource and the ordering semantics front-loaded. Nothing in it is redundant with the name or title.

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-only listing tool with annotations covering safety and no output schema, the description is close to sufficient. The remaining gaps — the meaning of "recent" (any time window?), the default for "limit", and the ordering guarantee when mixing backends — are the kind of detail an agent needs to call it predictably.

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 description coverage is 0%, so the description must carry the parameter burden, and it only partially does: it names the backend choices (with casing that differs from the enum values "zcode"/"codebuddy"/"qoder"/"all"). The "limit" parameter is never mentioned, nor is any default value or the maximum of 50, leaving an agent to guess the result-set size.

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 and resource ("List recent tasks") plus enumerated sources (CodeBuddy, Qoder, ZCode, all) and the ordering rule ("merged newest-first"). This implicitly separates it from single-backend siblings like zcode_list, but no sibling is named, so differentiation is inferred rather than explicit.

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?

The mention of "or all merged" implies the tool is the cross-backend aggregator and that per-backend alternatives exist, which is usable context. However, there is no explicit when-to-use vs. when-not, no pointer to zcode_list or swarm_backends, and no prerequisites stated.

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