Done Bear

Manage Project

project

Destructive

Create or change a project. action: "add" creates one (name required). action: "edit" updates the named project: only the fields given change, and an empty string clears description or target_date. action: "join" puts it in the caller's Your projects sidebar list and action: "leave" takes it out. Read projects with get_context.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Project name. Required on add; a rename on edit
`action`	Yes	What to do with the project
`status`	No	Project status (edit only)
`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. Required for edit, join and leave
`workspace`	No	Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
`description`	No	Project description (empty string clears it on an edit)
`target_date`	No	Target date (YYYY-MM-DD), or an empty string to clear it (edit only)
`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
`key`	Yes
`name`	Yes
`action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 5, 2026

addedOutput schema / properties / key / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / key / type

Removed value: -[
-  "string",
-  "null"
-]

addedOutput schema / properties / name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / name / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed4 schema fields changedSep 30, 2026

removedOutput schema / properties / key / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / key / type

Added value: +[
+  "string",
+  "null"
+]

removedOutput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedSep 29, 2026

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"

AddedSep 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the bar is lower, yet the description adds real context: edit is a partial update, only supplied fields change, and an empty string explicitly clears description or target_date. It does not disclose permission requirements or the effect of leave on existing project data.

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?

Four tight sentences, front-loaded with the core purpose, then action semantics, then clearing behavior, then the read alternative. No filler or restatement.

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 9-parameter mutation tool with an output schema and full schema description coverage, the description covers the action space, partial-update and clear semantics, and the read alternative. Minor gaps remain around workspace/auth preconditions, but the schema handles those.

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 baseline is 3, but the description meaningfully expands the terse action enum ('What to do with the project') into concrete semantics for each value, and restates the name-required-on-add rule. It adds value beyond the schema for the central 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?

States a specific verb pair and resource ('Create or change a project') and then enumerates the four action values with their distinct effects, so an agent can distinguish add/edit/join/leave without opening the schema. It also names get_context as the read path, separating this mutation tool from 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?

Gives explicit per-action conditions ('add' creates, 'edit' updates, 'join'/'leave' toggle sidebar membership) and routes reading to get_context. It stops short of stating when not to use the tool (e.g., permissions or prerequisites for joining), so it is strong but not fully complete.

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

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

Need Help?