Skip to main content
Glama
ihorponom

agentpack

by ihorponom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task_list

Read-only

Find Task Passport IDs or inspect task history. Filter by status/scope, limit results, and view open tasks by default; read-only.

Instructions

Find Task Passport ids or inspect task history. Without status lists open tasks; pass all: true for full history. compact and limit shorten the result. Filters combine with AND; current task is marked with an asterisk. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoInclude completed and abandoned tasks. Cannot combine with open: true or status.
jsonNoReturn structured JSON instead of formatted text.
openNoOnly active, parked, blocked, and verifying tasks (the default). Cannot combine true with status.
limitNoReturn at most this many matching tasks, newest updated first. Result metadata reports matched/returned/omitted counts.
scopeNoOne write-scope prefix filter or a non-empty array: unqualified paths select primary; id:path selects an additional repository. Matches CLI --scope.
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. Changed1 schema field changedv1.11.0
    • changedInput schema / properties / scope / description
      Previous value: -"One path or a non-empty array of paths overlapping task write scopes, matching CLI --scope semantics."New value: +"One write-scope prefix filter or a non-empty array: unqualified paths select primary; id:path selects an additional repository. Matches CLI --scope."
  2. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / all
      Added value: +{
+  "description": "Include completed and abandoned tasks. Cannot combine with open: true or status.",
+  "type": "boolean"
+}
    • changedInput schema / properties / open / description
      Previous value: -"Only active, parked, blocked, and verifying tasks. Cannot combine true with status."New value: +"Only active, parked, blocked, and verifying tasks (the default). Cannot combine true with status."
  3. 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"
+    }
+  ]
+}
  4. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / json / description
      Added value: +"Return structured JSON instead of formatted text."
  5. First observedv1.3.0

TDQS

A3.9/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, and the description reinforces 'Read-only'. Beyond that it adds genuinely non-structured behavior: AND-combination of filters, the asterisk marking the current task, and the fact that compact/limit shorten output. These are useful traits the schema alone does not fully 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?

Five short, front-loaded clauses with essentially no filler; the primary capability and default come first. The telegraphic style is efficient but occasionally terse enough to require schema consultation.

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 7-param, no-required-param read tool with no output schema, the description covers defaults, full-history mode, filter combination, and result-shortening options. Return-format details are delegated to the json/compact parameters, which is acceptable, so nothing critical is missing.

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 100%, so all seven parameters are already documented with default and conflict rules. The description only lightly restates status/all/compact/limit behavior, adding no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 leads with a concrete verb and resource mix ('Find Task Passport ids or inspect task history'), which distinguishes a listing/inspection tool from siblings like task_audit or task_status. It does not explicitly name or contrast those siblings, but the intent is unambiguous.

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 states the default behavior ('Without status lists open tasks') and the escape hatch ('pass all: true for full history'), which tells an agent when to reach for each mode. It stops short of naming an alternative sibling or stating exclusions, so it lands just below the top tier.

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