Done Bear MCP

Bulk Complete Tasks

task_bulk_done

Destructive

Mark multiple tasks as complete at once (max 50 task numbers per call). Confirm the number list with the user first: this is undone one task_reopen at a time, so a wrong 50-task set is a 50-call cleanup.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	Yes	Array of workspace-scoped task numbers
`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

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`count`	Yes
`tasks`	Yes	Every task the call changed, in the order it was given
`action`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds valuable behavioral context: a bulk mistake means a 50-call cleanup via task_reopen. It also instructs the agent to confirm the number list with the user before proceeding, which is important safety guidance beyond the structured hints.

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 with no filler. The primary action and batch limit are front-loaded, followed immediately by the critical confirmation and undo-cost warning. Every sentence earns its place.

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 bulk destructive mutation tool, the description covers the essential decision factors: the batch size limit, user confirmation requirement, and the practical cost of a mistake. The input schema and output schema cover parameter shapes and return values, so nothing necessary for safe invocation 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?

The schema already provides full parameter documentation: ids are workspace-scoped task numbers with minItems 1 and maxItems 50, and context is described as an explanation of the call. The description restates the 50-item cap but adds no new parameter-level meaning. Baseline 3 is appropriate because schema coverage is complete.

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 states a specific verb and resource: 'Mark multiple tasks as complete at once.' It also distinguishes this from single-task operations by emphasizing 'multiple' and 'at once,' which separates it clearly from sibling tools like task_done and task_reopen.

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?

The description gives clear context for when this tool is appropriate: when completing multiple tasks in a single call. It also provides an important usage caveat—confirm the list with the user first and be aware that undo requires one task_reopen call per task. It does not explicitly name task_done as the single-task alternative, but the bulk-vs-single contrast is effectively implied.

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?