Done Bear

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

A5/5.0

Behavior5/5

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

Beyond the annotations (which only indicate the tool is not read-only and not destructive), the description discloses meaningful behavior: new items start unchecked, are appended after existing ones, batch order is preserved, and parallel single calls may not preserve order. This gives the agent a clear mental model of execution semantics.

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 dense sentences with no filler. It front-loads the core behavior, then provides focused parameter guidance with a clear, emphasized recommendation. Every clause 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?

Given the schema fully documents required and optional parameters, and an output schema exists, the description supplies the missing behavioral context: append semantics, initial unchecked state, and ordering guarantees. An agent has everything it needs to invoke this tool correctly and avoid the parallel-call ordering pitfall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema covers 100% of parameters, the description adds critical semantic value by explaining the relationship between `title` and `titles`, when to choose each, and the ordering guarantees. This is exactly the kind of practical distinction that helps an agent pick the right parameter combination.

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: 'Add checklist items to a task'. It also distinguishes this tool from sibling tools like checklist_done, checklist_edit, and checklist_remove by clearly stating the add behavior, including that items start unchecked and append after existing ones.

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?

The description gives explicit usage guidance: use `title` for one item or `titles` for several, and ALWAYS batch multi-item adds into one call to preserve order. It explains the consequence of parallel single adds (arrival order, not list order), which is actionable and prevents a common mistake.

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

Disambiguation4/5

Tools are grouped cleanly by resource (task, checklist, comment, label, project, attachment), so most actions have an obvious owner. The main ambiguities are task_list vs. search and checklist_done vs. checklist_edit, but the descriptions call out the intended boundaries clearly enough to avoid frequent misselection.

Naming Consistency4/5

The dominant resource_verb pattern (task_add, task_edit, checklist_list, comment_remove, project_join) is consistent and predictable. A few outliers like get_context, guide, search, and task_attachment_list break the pattern, but the naming remains readable and mostly uniform.

Tool Count2/5

At 35 tools, this is a very large surface for an agent to choose from and exceeds the 25-tool threshold where count becomes a liability. The tools are well organized, but the repeated verb families across six resources make the total feel heavy even though each tool is plausibly justified.

Completeness4/5

The core task lifecycle is well covered: create, show, edit, list, complete, reopen, archive, assign, and bulk operations, plus full checklist, comment, label, and attachment workflows. Notable gaps are the lack of an explicit unarchive/restore path and no label edit/delete, but these are minor enough that agents can usually work around them.

Resources

Need Help?