Skip to main content
Glama

list_tasks

Collect checkbox tasks from every vault note or a single folder, leaving out completed tasks unless include_done=true.

Instructions

Collect checkbox tasks from every note in the vault, or from one folder. Finished tasks are left out unless include_done=true.

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
folderNo
include_doneNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral weight, and it does disclose the scan scope (every note in the vault) and the default filtering rule, which is real context. However, it never states that this is a non-mutating read, says nothing about the cost or result volume of a vault-wide scan, and gives no hint about recursion into subfolders.

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?

A single sentence with the scope stated first and the filtering exception trailing. No filler, no restatement of the tool name, and both parameters are covered in one clause each.

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, so return-value explanation is not required, and the description covers scope and filtering. Remaining gaps are minor: path format for 'folder', whether subfolders are traversed, and confirmation that the operation is read-only.

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 description coverage is 0%, so the description must explain both parameters — and it does: 'folder' is framed as restricting to 'one folder', and 'include_done' is explained by the finished-task exclusion rule. It stops short of specifying path format or what a null/omitted folder does beyond the implied vault-wide default.

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 names a concrete verb and resource — 'Collect checkbox tasks' — and states the scope explicitly: 'from every note in the vault, or from one folder.' This clearly separates it from write-oriented siblings like add_task or capture, though it never names an alternative directly.

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 usable selection context: the default is a vault-wide sweep, and passing a folder narrows to one folder. It also states when results are filtered ('finished tasks are left out unless include_done=true'), which tells the agent how to vary the call. There are no explicit exclusions or named alternatives, which keeps it below a 5.

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