Skip to main content
Glama
Sign In
things3-mcp

things3-mcp

by snellingio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_tasks

List tasks from the Today list or a specific project in Things 3. Specify 'today' for current tasks or provide a project ID for a project's tasks.

Instructions

List tasks from Today or from one project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "view": "<view>"
    },
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYesUse "today" for the Things Today list or "project" for one project.
project_idNoRequired for the project view and omitted for the today view.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It states only the action and scope, but does not disclose whether the operation is read-only, what permissions are needed, what the return format is, or any limitations such as pagination or inclusion of completed tasks. This is a significant gap for a listing tool.

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?

The description is a single sentence that is clear and to the point, with no wasted words. It effectively communicates the tool's core function in minimal space.

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

Completeness3/5

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

While the tool is simple and the schema covers parameters well, there is no output schema and the description does not mention any behavioral context or return details. Given the simplicity, it is minimally adequate but lacks explicit guidance on what the agent should expect.

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?

The input schema covers both parameters with descriptions, achieving 100% schema description coverage. The tool description adds no extra parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') and resource ('tasks') and clarifies the two possible scopes ('Today' or 'one project'). This clearly distinguishes it from sibling tools like list_projects (which lists projects) and create/update tasks.

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 this tool is used to list tasks, but it does not explicitly state when to use it over alternatives like list_projects, nor mention exclusions. The schema clarifies the view parameter, but the tool-level description gives no direct when-to-use guidance.

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