Skip to main content
Glama
ihorponom

agentpack

by ihorponom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task_list

Read-only

Retrieve task history or find Task Passport IDs by filtering open tasks, status, or scope. Read-only inspection of task progress with optional result limits.

Instructions

Find Task Passport ids or inspect task history. Prefer open: true and compact: true for open work; optionally limit the result. No arguments lists all history with legacy formatting. Filters combine with AND; current task is marked with an asterisk. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonNoReturn structured JSON instead of formatted text.
openNoOnly active, parked, blocked, and verifying tasks. Cannot combine true with status.
limitNoReturn at most this many matching tasks, newest updated first. Result metadata reports matched/returned/omitted counts.
scopeNoOne path or a non-empty array of paths overlapping task write scopes, matching CLI --scope semantics.
statusNoOne status or a non-empty array of statuses (OR within this filter).
compactNoOmit branch/scope in text or JSON whitespace; JSON fields remain unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.6.8
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "Omit branch/scope in text or JSON whitespace; JSON fields remain unchanged.",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Return at most this many matching tasks, newest updated first. Result metadata reports matched/returned/omitted counts.",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / open
      Added value: +{
+  "description": "Only active, parked, blocked, and verifying tasks. Cannot combine true with status.",
+  "type": "boolean"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "One path or a non-empty array of paths overlapping task write scopes, matching CLI --scope semantics.",
+  "oneOf": [
+    {
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "items": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "minItems": 1,
+      "type": "array"
+    }
+  ]
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "One status or a non-empty array of statuses (OR within this filter).",
+  "oneOf": [
+    {
+      "enum": [
+        "active",
+        "parked",
+        "blocked",
+        "verifying",
+        "completed",
+        "abandoned"
+      ],
+      "type": "string"
+    },
+    {
+      "items": {
+        "enum": [
+          "active",
+          "parked",
+          "blocked",
+          "verifying",
+          "completed",
+          "abandoned"
+        ],
+        "type": "string"
+      },
+      "minItems": 1,
+      "type": "array"
+    }
+  ]
+}
  2. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / json / description
      Added value: +"Return structured JSON instead of formatted text."
  3. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the 'Read-only.' sentence is somewhat redundant, but the description adds real behavioral context: no-argument default behavior (all history, legacy formatting), AND-combination of filters, and the asterisk marking the current task. These details exceed what the annotations convey.

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 definition is compact and front-loaded, leading with purpose and then guidance. Sentences are dense but each carries information; the only near-waste is repeating the read-only status already in annotations.

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 read-only list tool with full schema coverage and no output schema, the description supplies the essentials: default behavior, filter composition, defaults to prefer, and result-limit hints. It is complete enough to call correctly, with only minor gaps around relationship to sibling listing tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds genuinely useful cross-parameter semantics not in the schema: 'Filters combine with AND' and the no-argument default behavior. This clarifies how open, status, scope, and limit interact rather than just restating field-level docs.

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 states a specific verb and resource combination: 'Find Task Passport ids or inspect task history.' An agent can tell this is a read/list tool, though it never explicitly distinguishes itself from nearby siblings such as task_status or task_audit, leaving some ambiguity about when to prefer it.

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?

It gives concrete usage advice: 'Prefer open: true and compact: true for open work' and notes that no arguments lists all history. This is clear contextual guidance, but it stops short of naming alternatives or stating when NOT to use the tool versus task_status/task_audit.

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