Skip to main content
Glama

List Tasks

list_tasks

Lists active project tasks and filters them by phase, status, or priority to help you review work and identify pending, blocked, or completed items.

Instructions

List all active tasks, optionally filtered by phase or status.

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

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
phaseNoFilter by phase name.
statusNoFilter by status (pending, in_progress, blocked, completed).
priorityNoFilter by priority (critical, high, medium, low).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden and delivers very little: it never confirms read-only safety, does not explain whether completed or archived tasks are excluded, and offers no note on result size or ordering. The one behavioral hint ('active') is actually muddied by the status filter, which lists 'completed' as an accepted value, leaving the agent unsure whether completed tasks can ever appear.

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?

It is a single front-loaded sentence with no filler, and the core action is stated first with the modifiers trailing. The brevity is efficient rather than padded, though it borders on under-specification for a tool with four filter parameters.

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?

Because an output schema exists, return values need not be explained, but the description still leaves key gaps for a filtered-list tool with no annotations: the meaning of 'active' versus the 'completed' status filter, and the role of the path and priority parameters. An agent can call it, but may mis-scope its query.

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 four parameters (including path and priority) are already documented in the schema, setting the baseline at 3. The description adds no syntax, matching behavior, or combination guidance beyond restating two of the four filters, and notably omits the priority filter that the schema exposes.

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 gives a specific verb and resource ('List all active tasks') plus the optional narrowing dimensions, so an agent immediately knows this is a read/list operation over tasks. It does not differentiate itself from closely related siblings such as blocked_tasks, next_task, or list_phases, and the qualifier 'active' is left undefined.

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

Usage Guidelines2/5

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

The phrase 'optionally filtered by phase or status' hints at how to narrow results but never states when to reach for this tool versus blocked_tasks or next_task, nor any precondition for calling it. An agent must infer that this is the general listing entry point from the name alone.

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