Skip to main content
Glama

Done Bear

by com.donebear
OverviewDiscussionsAdmin

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, and passing nextCursor back as cursor reads the next page. To find a task by its words across every view use search instead, and task_show for one task's checklist, comments and files.

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.

  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.9/5.0
Behavior5/5

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

Discloses behaviors beyond the readOnlyHint/destructiveHint annotations: ordering rules (recency; completion time for done tasks), view/state overrides for logbook and trash, search-based reordering, and pagination semantics (limit/hasMore/nextCursor). This gives the agent a clear model of what happens and what to expect.

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 dense yet efficient: every sentence covers a distinct aspect (purpose/ordering, filtering semantics, pagination, sibling routing). It is front-loaded with the primary action and resource, and contains no filler or redundancy.

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?

With a rich output schema and read-only annotations present, the description fills the important gaps: ordering, view/state interplay, pagination, and alternative tool routing. An agent has enough context to call the tool correctly for filtering and paginated iteration without further clarification.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining how ordering is affected by state/view, how `search` changes the result order, and how `cursor`/`limit` pagination behaves. It does not repeat parameter defaults or types, which the schema already covers.

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?

States a specific verb ('List') and resource ('tasks in the workspace'), plus the ordering behavior (most recently updated first). Explicitly distinguishes itself from sibling tools by pointing to 'search' and 'task_show', so an agent can tell them apart immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit routing: 'To find a task by its words across every view use search instead, and task_show for one task's checklist, comments and files.' It also clarifies when to use logbook/trash views and how the `search` param interacts with the existing filter, leaving no ambiguity about selection.

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
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources