Skip to main content
Glama

task_list

Search and filter scoped Taskwarrior tasks, defaulting to open tasks in the current project ordered by urgency; use stale to surface items untouched for 60+ days.

Instructions

Search/filter tasks in scope. Defaults to open tasks in this folder's project, most urgent first. stale:true shows tasks untouched for 60+ days.

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

Input Schema

NameRequiredDescriptionDefault
cwdNoSession folder (absolute path). Filled in by the OpenCode plugin; other clients pass the working folder.
jobNoOverride: job (e.g. acme). Normally derived from the session folder.
kindNo
repoNoOverride: repo within the job. Normally derived from the session folder.
tagsNo
limitNo
staleNo
searchNoPlain text, case-insensitive, matches description, context and notes.
statusNo
claimedNo
projectNoOverride: exact project job.repo.
priorityNo
all_projectsNoCross-project view. Only for explicit global review.
include_notesNoAdd the last 2 notes under each task.
waiting_on_ownerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the default result set (open tasks), default scope (this folder's project), default ordering (most urgent first), and the exact stale threshold of 60+ days — none of which the schema states. It omits pagination/limit behavior and the return shape, which keeps it short of a 5.

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?

Three short sentences, front-loaded with purpose then defaults then the stale case; almost no waste. The telegraphic "stale:true" phrasing is efficient but slightly abrupt.

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

Completeness2/5

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

A 15-parameter query tool with no annotations and no output schema needs more than three sentences of context. The description leaves most filter semantics and the result shape (paging, ordering ties, note inclusion) unexplained.

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?

With 15 parameters and only 47% schema description coverage, the description should compensate but only explains `stale` and the defaults for `status`/project scope. Filters such as `claimed`, `waiting_on_owner`, `kind`, `tags`, `priority`, and `limit` get no meaning from either source.

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 ("Search/filter tasks") plus a scope qualifier, so an agent can tell it apart from task_get or task_create. The sibling differentiation is implicit rather than named, and "in scope" is only clarified by the following sentence.

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?

Gives a useful default condition (open tasks in this folder's project) and one narrowing case (stale:true for 60+ days untouched), which implies when to use it. It never says when to prefer task_get versus this list, nor when all_projects or claimed/waiting_on_owner filters are appropriate.

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