Done Bear MCP

List Task Comments

comment_list

Read-only

Read the comment thread on a task, oldest first, with each comment's id, author and whether it has been edited. Comments are the discussion around a task; the task's own notes are where its content belongs.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	Yes	Workspace-scoped task number, encoded as a string
`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
`count`	Yes
`total`	Yes
`taskId`	Yes
`hasMore`	Yes	True when more results matched than were returned
`comments`	Yes

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds useful behavioral details: comments are returned oldest first and include the edited flag. It does not mention pagination, limits, or other access behavior, but these are minor given the read-only annotation and existing output schema.

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?

Two sentences with no filler. The core operation and ordering are front-loaded in the first sentence, and the conceptual distinction in the second sentence earns its place. Nothing is redundant with annotations or schema.

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 simple read-only list tool with an output schema and full schema coverage, the description covers purpose, ordering, and the distinction from notes. It does not explicitly mention pagination or alternative tools by name, but these are not critical given the tool's simplicity and the provided annotations.

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 input schema already documents all parameters. The description does not add parameter-level meaning, which is acceptable because the schema carries that burden. No further compensation is needed.

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 ('read'), a specific resource ('the comment thread on a task'), and concrete output characteristics (oldest first, id, author, edited status). It also distinguishes itself from task-note content, making it clear this is about the discussion thread, not the task's own notes.

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 on when to use this tool: when you need the discussion around a task. It also notes that the task's own notes are where its content belongs, implying task_show or similar is for notes. However, it does not explicitly name an alternative tool or state a direct when-not-to-use condition.

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?