Done Bear MCP

Add Checklist Items

checklist_add

Add checklist items to a task; items start unchecked and append after existing ones. Pass title for one item or titles for several: a titles batch keeps the given order, so ALWAYS add a multi-item list in one call rather than one call per item (parallel single adds land in arrival order, not list order).

Input Schema

TableJSON Schema

Name	Required	Description
`task`	Yes	Workspace-scoped task number, encoded as a string
`title`	No	Checklist item title
`titles`	No	Several checklist item titles, 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."
`workspace`	No	Workspace id, slug, or name
`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	Default
`ok`	Yes
`count`	Yes
`items`	Yes
`taskId`	Yes

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only provide readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description goes beyond that by disclosing the key behavioral traits: items start unchecked, they append after existing items, and batched `titles` preserve order while parallel single adds do not. This is material context that an agent cannot infer from the schema alone.

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 two sentences, directly front-loaded with the action and effect, and contains no filler. The critical batch-ordering warning is placed exactly where it needs to catch the agent's attention.

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 a mutating tool with a fully described schema and an output schema present, the description covers the essential facts: what items are added, their initial state, their placement, and how to preserve order for multiple items. No critical calling requirement is left unaddressed.

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 already describes all parameters, including task, title, titles, context, workspace, and idempotency_key. Schema description coverage is 100%, so the baseline is 3. The description reinforces the title/titles distinction and ordereing semantics, but does not add significant parameter-level meaning beyond what the schema already documents.

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 clearly states the verb and resource: it adds checklist items to a task. It further specifies the behavior (items start unchecked, append after existing) and distinguishes the single-item vs multi-item call variants, making it clearly different from sibling tools like checklist_edit or checklist_remove.

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 gives explicit guidance on when to use `title` vs `titles`, and strongly instructs that multi-item lists should always be added in one batch call because parallel single adds do not guarantee order. It does not explicitly name sibling alternatives, but the add-vs-edit/remove distinction is obvious from the title and operation.

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

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.6/5.0

Disambiguation4/5

Most tools are cleanly separated by resource and action, and each family (checklist, comment, label, project, task) follows the same shape. The main blur is between search and task_list's optional search filter, and convenience tools like checklist_done overlap with checklist_edit.

Naming Consistency4/5

The dominant convention is snake_case noun_verb (task_add, checklist_list, comment_remove), with consistent verb families across resources. A few outliers like get_context, search, and guide break the pattern, but overall the naming is predictable and readable.

Tool Count2/5

At 35 tools, this is a heavy surface for a task-management server and exceeds the 25-tool threshold. Several tools are convenience variants (task_done vs task_bulk_done, checklist_done vs checklist_edit) that could be consolidated or represented as parameters.

Completeness4/5

The core task lifecycle is well covered: create, show, edit, complete, reopen, archive, list, assign, and bulk operations, with full checklist and comment CRUD. Notable gaps are label deletion/renaming, project deletion, and search being limited to tasks, but these are minor for the apparent product scope.

Resources

Need Help?