Skip to main content
Glama

Done Bear

by com.donebear
OverviewDiscussionsAdmin

Add Task

task_add

Create a new task. An explicit when selects its start placement: today, inbox, upcoming, anytime, or someday; upcoming schedules tomorrow. Without when, a deadline or omitted timezone selects anytime first. Otherwise, a project or team selects inbox; an unfiled task selects today. Pass the user's known IANA timezone to resolve calendar days. Use when: "inbox" for capture without a commitment to today. deadline uses YYYY-MM-DD. Optionally assign the task, attach existing labels, or pass checklist item titles in checklist; their order is preserved. The result's view reports the selected start placement, while a due or overdue deadline can make the task appear in Today. To change an existing task, use task_edit for fields or the available checklist tools for items. Search first when the user may be describing an existing task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoTeam id, key, or name
whenNoGTD 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.
notesNoTask description/notes
titleYesTask title
labelsNoLabels to attach (each a label id, title, or id prefix)
contextYesExplain 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."
projectNoProject id, key, or name to assign this task to
assigneeNoMember (user id, name, or email) or task agent (id or name) to assign the task to
deadlineNoDue date in YYYY-MM-DD format
timezoneNoIANA 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.
checklistNoChecklist item titles to create on the task, kept in the given order
workspaceNoWorkspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
idempotency_keyNoStable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
okYes
viewYes
titleYes
numberYes
checklistCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / assignee / description
      Previous value: -"Member user id, name, or email to assign the task to"New value: +"Member (user id, name, or email) or task agent (id or name) to assign the task to"
  2. Changed1 schema field changed
    • 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"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, closed-world), so the remaining burden is light. The description still adds non-obvious behavior: the result's `view` reports the selected placement, and a due/overdue deadline can surface the task in Today, plus the full fallback cascade for placement. It does not mention permission or rate-limit behavior, but those are not the core risk here.

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 primary action and placement rules are front-loaded, and most sentences carry decision-relevant information. It is long but dense; the main waste is the placement paragraph partially duplicating the already-verbose `when` schema description.

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 with an output schema, the hard part is the placement algorithm, and the description covers it exhaustively, including the exceptions (deadline/missing timezone, project/team filing). Return values are omitted but an output schema exists, so that is appropriate.

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 baseline is 3. The description's parameter detail (the `when` enum semantics, "deadline uses YYYY-MM-DD", checklist order preservation) largely restates what the schema's `when`, `deadline`, and `checklist` descriptions already say, adding little beyond 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?

Opens with a specific verb+resource ("Create a new task") and immediately separates itself from siblings by naming task_edit for modifications and the checklist tools for existing items. An agent can distinguish it from task_edit, task_show, or search without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes alternatives: use task_edit to change an existing task, checklist tools for items, and "Search first when the user may be describing an existing task." It also gives the capture-vs-commit condition for `when: "inbox"`, so usage decisions are spelled out rather than inferred.

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

All Done Bear toolsInspect
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