mcp-workspace

List tasks

tasks_list

Read-only

List tasks in the workspace, showing open items by default and optionally filtering by tag or status to locate relevant work.

Instructions

List tasks, open ones by default, optionally only those with a tag.

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

Input Schema

Name	Required	Description	Default
`tag`	No
`status`	No		open

Output Schema

Name	Required	Description	Default
`tasks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful default that only open tasks are returned unless specified otherwise, but says nothing about ordering, result size, or how 'done'/'all' behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the action and immediately followed by the default behavior and the one meaningful filter. Nothing redundant.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to convey filtering semantics. It does that adequately for a two-parameter list tool, with minor gaps around status values and result ordering.

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 0%, so the description has to carry parameter meaning. It conveys that tag is an optional filter and that status defaults to open, but never names the status values (open/done/all) or the tag format, leaving the enum to speak for itself.

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 ('List tasks') plus the default scope (open only) and the optional tag filter. Siblings are all notes_* tools, so there is no real overlap to disambiguate; still, the purpose 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 Guidelines3/5

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

The description implies when this tool is used (enumerating tasks, narrowing by tag) and notes the default of open tasks, but gives no explicit guidance on when to prefer a different tool or when tags should not be used.

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

Deploy Server