Skip to main content
Glama
NicolasPrimeau

Artel

by NicolasPrimeau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

task_list

Read-only

List and filter tasks by status, project, or tag to find work that needs doing. Use unblocked to show only actionable tasks with no incomplete dependencies.

Instructions

DEPRECATED: the harness owns this now, Claude Code discovers peers and manages its own task list. Still works; not where new work should go.

List tasks. Call with status="open" to find work that needs doing.

Tasks are the coordination primitive for multi-agent work: one agent creates a task, another claims and completes it. Check for open tasks before creating new ones. Use unblocked=True to filter to only tasks whose dependencies are all completed.

Args: status: open, claimed, completed, or failed. Omit for all. project: Filter by project name. tag: Filter to tasks carrying this tag. unblocked: If True, only return tasks with no incomplete dependencies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter to tasks carrying this tag.
statusNoopen, claimed, completed, or failed. Omit for all.
projectNoFilter by project name.
unblockedNoIf True, only return tasks with no incomplete dependencies.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.40.1
    • addedInput schema / properties / unblocked
      Added value: +{
+  "default": false,
+  "description": "If True, only return tasks with no incomplete dependencies.",
+  "title": "Unblocked",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.17.7
    • addedInput schema / properties / tag
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter to tasks carrying this tag.",
+  "title": "Tag"
+}
  3. Addedv0.17.0
  4. Removedv0.16.1
  5. Addedv0.9.0
  6. Removedv0.7.0
  7. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive behavior. The description adds the deprecation status and explains the unblocked filter semantics, which goes beyond the schema. It does not describe return format, but output schema exists to cover that.

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?

The description is front-loaded with the deprecation notice and a clear one-line purpose, followed by usage guidance and parameters. It is slightly verbose with the coordination primitive paragraph, but structured and informative without being excessive.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the annotations, output schema, and 100% parameter coverage, the description fully equips an agent to use the tool correctly. It explains the deprecation, usage context, and filtering options, leaving no critical gaps.

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 coverage is 100%, and the description repeats the parameter descriptions verbatim without adding new meaning. The 'unblocked' explanation is identical to the schema, so no extra value is provided beyond the 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?

The description clearly states the tool 'List tasks' and explains it as the coordination primitive for multi-agent work, distinguishing it from task_get (single task) and task_create. The deprecation notice adds clarity about its current role, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Explicitly states when to use (check for open tasks before creating new ones) and when not to use ('not where new work should go' due to deprecation). It also provides specific filter recommendations (status='open', unblocked=True) and explains the context of task coordination.

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

Deploy Server

Other Tools