Skip to main content
Glama

Done Bear

by com.donebear

List Tasks

task_list
Read-only

List tasks in the workspace, most recently updated first. Completed tasks are ordered by completion time, newest first. Filter by view (inbox, today, upcoming, anytime, someday, logbook, trash) and/or state (open, done, archived, all); search ranks matches within that filter. view: "logbook" reads completed tasks and view: "trash" archived ones, whatever state says. Returns up to limit tasks; hasMore is true when more matched than were returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoFilter by GTD view bucket. logbook and trash read the completed and archived tasks regardless of `state`
limitNoMax results
stateNoFilter by task stateopen
cursorNoOpaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page.
searchNoRanked lexical search over title/description; when set, results are ordered by relevance instead of recency
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
timezoneNoIANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known.
workspaceNoWorkspace id, slug, or name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
tasksYes
totalYes
hasMoreYesTrue when more results matched than were returned
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / tasks / items / properties / completedAt
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Completion instant in UTC (ISO 8601), or null for an unfinished task"
+}
    • changedOutput schema / properties / tasks / items / required
      Previous value: -[
-  "assigneeId",
-  "completed",
-  "deadline",
-  "description",
-  "id",
-  "number",
-  "projectId",
-  "startDate",
-  "state",
-  "teamId",
-  "title",
-  "view"
-]New value: +[
+  "assigneeId",
+  "completed",
+  "completedAt",
+  "deadline",
+  "description",
+  "id",
+  "number",
+  "projectId",
+  "startDate",
+  "state",
+  "teamId",
+  "title",
+  "view"
+]
  2. Changed4 schema fields changed
    • changedInput schema / properties / view / description
      Previous value: -"Filter by GTD view bucket"New value: +"Filter by GTD view bucket. logbook and trash read the completed and archived tasks regardless of `state`"
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "inbox",
-  "anytime",
-  "today",
-  "upcoming",
-  "someday"
-]New value: +[
+  "inbox",
+  "anytime",
+  "today",
+  "upcoming",
+  "someday",
+  "logbook",
+  "trash"
+]
    • addedOutput schema / properties / tasks / items / properties / completed
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The date (YYYY-MM-DD) the task was completed, in the requested timezone. Null while it is still open"
+}
    • changedOutput schema / properties / tasks / items / required
      Previous value: -[
-  "assigneeId",
-  "deadline",
-  "description",
-  "id",
-  "number",
-  "projectId",
-  "startDate",
-  "state",
-  "teamId",
-  "title",
-  "view"
-]New value: +[
+  "assigneeId",
+  "completed",
+  "deadline",
+  "description",
+  "id",
+  "number",
+  "projectId",
+  "startDate",
+  "state",
+  "teamId",
+  "title",
+  "view"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark the call read-only and non-destructive; the description adds substantial behavioral detail beyond that: sort order, completed-task ordering, view/state precedence, and hasMore pagination semantics. No contradiction with annotations.

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?

Four dense sentences front-load the core behavior, and every clause contributes: ordering, filters, search ranking, view/state override, and pagination. The enum list repetition is acceptable because it saves the agent from reopening the schema.

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?

For an 8-parameter tool with a full output schema and read-only annotations, the description covers the essential behaviors an agent needs to call it correctly: ordering, filter semantics, search behavior, view/state precedence, and pagination results. Remaining parameters are fully documented in the schema.

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 coverage is 100%, so the baseline is 3. The description earns a 4 by adding meaning beyond the schema: it clarifies that logbook/trash views read completed/archived tasks regardless of state, and that search ranks within the current filter.

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 clearly identifies the operation and scope: 'List tasks in the workspace' with explicit ordering and filtering behavior. It does not explicitly differentiate task_list from sibling tools like task_show or search, so it falls short of a 5.

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?

Provides concrete usage context: how view and state filters interact, and that logbook/trash override state. It does not name alternatives or state when-not-to-use conditions, so explicit routing guidance is missing.

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

All Done Bear toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools map to clearly distinct resources and actions: task lifecycle verbs, sub-resource tools (attachment, checklist, comment), and search are easy to tell apart. The only mild overlaps are search vs task_list's built-in search parameter and get_context vs task_list for recent tasks, but the descriptions give enough guidance to avoid frequent misselection.

Naming Consistency3/5

Task operations consistently follow a task_verb pattern, but other tools use bare resource nouns (attachment, checklist, comment, project), plus get_context, guide, label_create, and search break the pattern further. The names are readable, but the convention is mixed rather than uniform.

Tool Count5/5

At 15 tools, the set sits at the upper end of the well-scoped range but each tool has a distinct responsibility: task lifecycle, search, sub-resources, project/label management, context, and guidance. None feel redundant, and the count matches the breadth of the task-management domain.

Completeness3/5

Core task workflows are well covered: create, read, update, complete, reopen, archive, list, and search, plus comments, checklists, and attachments. Notable gaps remain: labels only support creation, archived tasks have no explicit restore path, and projects cannot be deleted or archived.

Resources