Done Bear MCP

Add Task

task_add

Create a new task. The when parameter controls which GTD view it appears in: today (default), inbox, upcoming, anytime, or someday. A new task lands in Today unless you say otherwise, so pass when: "inbox" for a capture the user has not committed to doing today. Because the default is date-dependent, always pass the user's timezone — without it today is resolved in UTC. Dates use YYYY-MM-DD format. Optionally set an assignee, attach labels, and create checklist items at creation. For a task with sub-items (e.g. a shopping list), pass them in checklist in one call: their order is preserved exactly.

Input Schema

TableJSON Schema

Name	Required	Description
`team`	No	Team id, key, or name
`when`	No	GTD view bucket: today, inbox, upcoming, anytime, someday. Omitting this means today, with three exceptions: a deadline or a missing timezone falls back to anytime (the work is due later, or today cannot be resolved), and a project or team falls back to inbox (the task is already filed). Pass timezone to get today. Use "inbox" for a capture the user has not committed to doing.
`notes`	No	Task description/notes
`title`	Yes	Task title
`labels`	No	Labels to attach (each a label id, title, or id prefix)
`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."
`project`	No	Project id, key, or name to assign this task to
`assignee`	No	Member user id, name, or email to assign the task to
`deadline`	No	Due date in YYYY-MM-DD format
`timezone`	No	IANA 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.
`checklist`	No	Checklist item titles to create on the task, kept in the given order
`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
`id`	Yes
`ok`	Yes
`view`	Yes
`title`	Yes
`number`	Yes
`checklistCount`	Yes

TDQS

A3.9/5.0

Behavior4/5

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

Description discloses important behavior beyond annotations: new tasks default to Today, the default depends on timezone and falls back to UTC, and checklist order is preserved exactly. This adds material context on top of the minimal `readOnlyHint: false` and `destructiveHint: false` annotations.

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?

The description is front-loaded with 'Create a new task' and each subsequent sentence addresses a real usage pitfall. A small amount of redundancy with the schema's parameter descriptions, such as checklist order, keeps it from a perfect score.

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 13-parameter creation tool with an output schema and 100% schema coverage, the description covers the most consequential behaviors: default view, timezone sensitivity, and checklist use. The remaining parameters are well documented in the schema, leaving no critical gap for an agent to call the tool correctly.

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?

Schema description coverage is 100%, so the schema already documents all 13 parameters. The description adds useful emphasis on `when`, `timezone`, and `checklist`, but mostly reinforces schema details rather than introducing new semantics, so the baseline of 3 is appropriate.

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 opens with 'Create a new task,' a specific verb and resource that clearly identifies the operation. It provides enough task-creation context to differentiate from task_edit and task_done, though it never explicitly names a sibling or states what it is not.

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?

Clear practical guidance is given: pass `when: "inbox"` for captures not committed to today, always include `timezone` to resolve today correctly, and use `checklist` in one call for sub-items. No explicit alternatives or exclusions are stated, but the context strongly implies this is for new tasks rather than modifications.

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?