Skip to main content
Glama

Done Bear MCP

by com.donebear.mcp
OverviewDiscussionsAdmin

Manage Task Comment

comment
Destructive

Write on a task's comment thread. action: "add" posts a comment, attributed to the connected user and visible to everyone in the workspace, so write it as a message to the user's teammates rather than a note to the user; nobody is notified. action: "edit" rewrites one of your own (only its author may, and it is then marked edited). action: "remove" deletes one permanently — comments have no Trash — so confirm with the user first. Read the thread with task_show and include: ["comments"].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoComment text. Required to add or edit
taskYesWorkspace-scoped task number, encoded as a string
actionYesWhat to do on the thread
commentNoComment UUID or prefix (>= 4 chars). Required to edit or remove
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."
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
actionYes
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only give the generic destructive/write profile; the description adds real behavioral context: attribution to the connected user, workspace-wide visibility, no notification sent, permanent deletion with no Trash, and the 'edited' marker on rewrites. It also warns that the audience is teammates, not the invoking user.

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?

Front-loads the resource, then handles actions in enum order with the destructive one last and the most cautionary detail attached to it. Every clause adds operational information; nothing is restated from the title or schema.

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?

An output schema exists, so return values need no explanation, and the 7-parameter surface is the only complexity left. The description covers the mutation lifecycle, audience, and reversibility, which is everything an agent needs to call it safely.

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, but the description maps action values to their parameter requirements by implication (body to post/rewrite, comment to edit/remove, task to all) and clarifies intent behind the destructive path. It stops short of explaining the UUID-prefix matching or idempotency semantics, which stay in 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?

States a concrete verb and resource ('Write on a task's comment thread') and then enumerates the three actions with their distinct effects. It explicitly distinguishes itself from task_show, which is named as the read path, so an agent can route without opening a sibling 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?

Each action carries its own when-to-use condition: add for posting a workspace-visible message, edit restricted to your own comment, remove only after user confirmation. It also names the alternative for reading the thread (task_show with include: ["comments"]), covering the when-not case.

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 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