Done Bear

Get Workspace Context

get_context

Read-only

Get a snapshot of the current workspace: task counts per view, recent open tasks, and every project, label, team and member. This is the tool that answers what is in the workspace and resolves a project, label, team or member by name — there is no separate list tool for those. Use it for that, not as a warm-up before every turn. For tasks themselves use task_list (a view), search (by words) or task_show (one task): the recent tasks here are only the latest few.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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."
`timezone`	No	IANA 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.
`workspace`	No	Workspace id, slug, or name
`tasks_limit`	No	Max recent open tasks to return
`projects_status`	No	Which projects to return	active

Output Schema

TableJSON Schema

Name	Required	Description
`teams`	Yes
`today`	Yes	Today's date (YYYY-MM-DD) in the requested timezone (UTC when none given)
`labels`	Yes
`members`	Yes
`projects`	Yes
`taskCounts`	Yes
`viewCounts`	Yes
`recentTasks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 4, 2026

addedInput schema / properties / projects_status

Added value: +{
+  "default": "active",
+  "description": "Which projects to return",
+  "enum": [
+    "active",
+    "done",
+    "archived",
+    "all"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / activeProjects

Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "id": {
-        "type": "string"
-      },
-      "key": {
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "targetDate": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "id",
-      "key",
-      "name",
-      "targetDate"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / projects

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "key": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "targetDate": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "key",
+      "name",
+      "status",
+      "targetDate"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "activeProjects",
-  "labels",
-  "members",
-  "recentTasks",
-  "taskCounts",
-  "teams",
-  "today",
-  "viewCounts"
-]New value: +[
+  "labels",
+  "members",
+  "projects",
+  "recentTasks",
+  "taskCounts",
+  "teams",
+  "today",
+  "viewCounts"
+]

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/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 covered. The description adds useful behavioral context: it returns a snapshot, includes only the latest few recent tasks, and is the sole resolver for projects/labels/teams/members. It does not detail pagination or exact response shape, but the output schema exists and the read-only nature is already annotated, so the added context is sufficient.

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 description is a single dense paragraph that front-loads the core purpose and scope, then adds usage guidance and sibling routing. It is slightly long but every sentence earns its place: the first sentence defines the snapshot contents, the second clarifies the resolver role, and the third gives explicit when-not-to-use guidance. No filler or repetition.

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 read-only snapshot tool with a rich output schema and full schema coverage, the description covers the essential context: what the tool returns, when to use it, and how it differs from siblings. It does not mention pagination or the exact meaning of 'recent', but the output schema and the explicit 'latest few' caveat make the tool callable correctly. A small gap is the lack of detail on how the timezone parameter affects the snapshot, but that is documented in the schema.

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 schema already documents all five parameters. The description adds minimal parameter-level meaning beyond the schema, though it does clarify the tool's overall scope. The timezone parameter's warning about UTC misclassification is in the schema, not the description. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 ('Get a snapshot') and resource ('current workspace'), enumerates exactly what is included (task counts per view, recent open tasks, projects, labels, teams, members), and explicitly distinguishes itself from sibling tools like task_list, search, and task_show. It also clarifies that it is the only tool for resolving projects/labels/teams/members by name, which fully disambiguates it 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 Guidelines5/5

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

The description gives explicit when-to-use guidance: use it to answer what is in the workspace and to resolve entities by name, and explicitly warns not to use it as a warm-up before every turn. It also names the alternatives for tasks (task_list, search, task_show) and states that the recent tasks here are only the latest few, so an agent knows when to prefer those siblings.

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?