Done Bear MCP

Manage Task Checklist

checklist

Destructive

Change the checklist on a task. action: "add" appends items, unchecked, after the existing ones: pass every title for a multi-item list in one call (titles keeps the given order, while parallel single adds land in arrival order). action: "edit" renames an item and/or checks it (completed: true) or unchecks it (completed: false). action: "remove" deletes one. Read the list, with each item's id and state, from task_show.

Input Schema

TableJSON Schema

Name	Required	Description
`item`	No	Checklist item UUID or prefix (>= 4 chars). Required to edit or remove
`task`	Yes	Workspace-scoped task number, encoded as a string
`title`	No	One item title to add, or the new title on an edit
`action`	Yes	What to do to the checklist
`titles`	No	Several item titles to add, kept in the given order (use instead of `title`)
`context`	Yes	Explain 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."
`completed`	No	Check (true) or uncheck (false) the item, on an edit
`workspace`	No	Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
`idempotency_key`	No	Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`count`	Yes
`items`	Yes	The items the call created or changed
`action`	Yes
`taskId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026
- addedOutput schema / properties / items / items / properties / title / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / title / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
Changed2 schema fields changedSep 30, 2026
- removedOutput schema / properties / items / items / properties / title / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / workspace / description

Previous value: -"Workspace id, slug, or name"New value: +"Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"

AddedSep 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description is consistent with that ('remove deletes one'). Beyond the annotations it discloses real behavior: appended items land unchecked after existing ones, and titles preserves order while parallel single adds land in arrival order. It omits auth/workspace prerequisites and retry semantics, which the schema covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then organized action-by-action, and the closing sentence points to the read path. The parenthetical about parallel single adds is slightly tangential but conveys a genuine ordering caveat, so it earns its place.

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?

For a 9-parameter mutation tool with an output schema, the description covers the operation semantics and where to read state, leaving workspace, idempotency, and return shape to structured fields. Nothing essential for correct invocation is missing, though prerequisites like workspace selection are not echoed.

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, but the description adds meaning beyond it: the title/titles choice, the ordering guarantee for titles versus parallel adds, and completed:true/false as check/uncheck on edit. The item parameter's role for edit/remove is left to the schema.

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 opening sentence names a specific verb and resource ('Change the checklist on a task') and the action breakdown makes each operation concrete. It distinguishes itself from siblings by routing reads to task_show, so an agent can separate mutation from inspection without opening either schema.

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 states what each action does and names task_show as the way to read item ids and state, which is the key alternative. It also guides batching ('pass every title for a multi-item list in one call'). It stops short of explicit when-not-to-use or prerequisite conditions such as the multi-workspace requirement.

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

All Done Bear MCP tools Inspect

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

Need Help?