Done Bear

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description reveals important behavioral details beyond the annotations: new tasks land in Today by default, the default is timezone-dependent, and checklist order is preserved. Since the annotations only provide basic false hints for read-only/open-world/destructive flags, the description carries the transparency burden and largely succeeds, though it does not mention authorization requirements or broader side effects.

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 compact and front-loaded, starting with the core operation before addressing the highest-risk semantics. Every sentence carries useful information, and there is no filler or repetition of schema details that are already fully stated.

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 13-parameter creation tool, the description covers the non-obvious behavioral details an agent would need: default GTD bucket, timezone handling, date format, and checklist creation semantics. The schema fully documents the remaining parameters, and the output schema covers return values, leaving no material gap for correct invocation.

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 coverage is 100%, so the baseline is 3, and the description adds meaningful extra semantics: what 'when' values mean, the interaction between the default and timezone, YYYY-MM-DD date formatting, and the guarantee that checklist order is preserved. These nuances go beyond the schema's property descriptions without needing to restate every parameter.

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 opens with a specific verb and resource: 'Create a new task.' It goes beyond the generic title by explaining the tool's scope around GTD views, checklist creation, labels, and assignees, which clearly distinguishes it from task_edit, task_assign, task_list, and other siblings.

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 clear contextual guidance for when to use the tool, such as passing 'when: inbox' for an uncommitted capture and always including the user's timezone to avoid UTC misclassification. It also advises passing sub-items as checklist items in one call, but it does not explicitly state when to prefer task_edit or other alternatives for modifying existing tasks.

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

All Done Bear 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.9/5.0

Disambiguation4/5

Most tools map to clearly distinct resources and actions: task lifecycle verbs, sub-resource tools (attachment, checklist, comment), and search are easy to tell apart. The only mild overlaps are search vs task_list's built-in search parameter and get_context vs task_list for recent tasks, but the descriptions give enough guidance to avoid frequent misselection.

Naming Consistency3/5

Task operations consistently follow a task_verb pattern, but other tools use bare resource nouns (attachment, checklist, comment, project), plus get_context, guide, label_create, and search break the pattern further. The names are readable, but the convention is mixed rather than uniform.

Tool Count5/5

At 15 tools, the set sits at the upper end of the well-scoped range but each tool has a distinct responsibility: task lifecycle, search, sub-resources, project/label management, context, and guidance. None feel redundant, and the count matches the breadth of the task-management domain.

Completeness3/5

Core task workflows are well covered: create, read, update, complete, reopen, archive, list, and search, plus comments, checklists, and attachments. Notable gaps remain: labels only support creation, archived tasks have no explicit restore path, and projects cannot be deleted or archived.

Resources

Need Help?