DontMynd

List tasks

list_tasks

Read-onlyIdempotent

List tasks, optionally filtered by location (this_week, next_week, backlog, past_week), week id (e.g. 2026-W27), tag name, or completion state. Returns at most limit tasks (default 50, maximum 200). Pass cursor (from next_cursor) or offset to page. The response includes has_more and next_cursor; cursor overrides offset when both are set.

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

Name	Required	Description
`tag`	No	Only tasks with this tag name
`limit`	No	Maximum tasks to return (default 50, max 200)
`cursor`	No	Opaque next_cursor from a previous list_tasks response. Overrides offset.
`offset`	No	Number of matching tasks to skip when cursor is omitted (default 0)
`week_id`	No	Only tasks in this week, e.g. 2026-W27
`location`	No	Only tasks in this location
`include_completed`	No	Include completed tasks (default true)

Output Schema

Name	Required	Description	Default
`count`	Yes
`tasks`	Yes
`has_more`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "next_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tasks": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "created_at": {
+            "type": "string"
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "is_completed": {
+            "type": "boolean"
+          },
+          "location": {
+            "type": "string"
+          },
+          "position": {
+            "type": "number"
+          },
+          "tag": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          },
+          "week_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "description",
+          "location",
+          "week_id",
+          "is_completed",
+          "position",
+          "tag",
+          "created_at",
+          "updated_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "tasks",
+    "has_more",
+    "next_cursor"
+  ],
+  "type": "object"
+}

First observedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description nonetheless adds genuinely useful non-obvious behavior: result caps (default 50, max 200) and the rule that cursor overrides offset when both are supplied.

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?

Three sentences, front-loaded with purpose, then pagination rules. No filler, and each sentence carries either filter scope or paging constraint.

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

Completeness5/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 safety, so the description only needed to cover filtering and paging semantics — which it does, including the cursor/offset precedence and the has_more/next_cursor hand-off. Nothing required to call it correctly is missing.

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 every parameter including the enum values and bounds is already documented. The description restates that content (defaults, max, filter meanings) and adds only the small clarification that the cursor comes from next_cursor and wins over offset; baseline 3 fits.

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?

Specific verb (List) plus resource (tasks) with an enumeration of the dimensions that can be filtered on, so an agent knows exactly what the tool retrieves. It never contrasts itself with the sibling search_tasks, so the boundary between browsing and searching is left implicit.

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?

Filter options imply the browse use case, and the cursor/offset guidance is operative, but there is no explicit statement of when to prefer this over search_tasks or get_task. Usage is inferable rather than stated.

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

All DontMynd tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?