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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>"
    },
    "name": "get_context"
  }
}

Input 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. Required when the account has more than one workspace: a call without it then fails and names the choices
`tasks_limit`	No	Max recent open tasks to return
`projects_status`	No	Which projects to return	active

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

Changed8 schema fields changedOct 5, 2026
- addedOutput schema / properties / projects / items / properties / targetDate / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / projects / items / properties / targetDate / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / recentTasks / items / properties / deadline / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / recentTasks / items / properties / deadline / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / recentTasks / items / properties / projectId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / recentTasks / items / properties / projectId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / recentTasks / items / properties / view / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / recentTasks / items / properties / view / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
Changed8 schema fields changedSep 30, 2026
- removedOutput schema / properties / projects / items / properties / targetDate / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / projects / items / properties / targetDate / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / recentTasks / items / properties / deadline / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / recentTasks / items / properties / deadline / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / recentTasks / items / properties / projectId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / recentTasks / items / properties / projectId / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / recentTasks / items / properties / view / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / recentTasks / items / properties / view / 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"

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

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds meaningful scope behavior beyond that: it is the only name-resolution path for projects/labels/teams/members, and it warns that returned tasks are only the latest few rather than a full task set.

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?

Three sentences, front-loaded with what the tool returns, then its unique resolution role, then the exclusion warning and alternatives. Every sentence carries distinct routing value and nothing is redundant.

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?

With an output schema present, annotations covering safety, and full schema coverage, the description only needs to carry the selection logic and scope caveats — which it does completely, including the multi-workspace name-resolution role and the 'latest few tasks' limitation.

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 context, timezone, workspace, tasks_limit and projects_status are all already documented with defaults, bounds and enum values. The description adds no parameter-level detail (e.g. timezone effect on view classification) beyond what the schema already states, so the baseline 3 is appropriate.

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?

Names a specific verb+resource ('Get a snapshot of the current workspace') and enumerates the contents (task counts per view, recent open tasks, projects, labels, teams, members). It explicitly distinguishes itself from siblings task_list, search, and task_show, so an agent can select it without consulting other schemas.

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?

States when to use it ('answers what is in the workspace', 'resolves a project, label, team or member by name'), when NOT to use it ('not as a warm-up before every turn'), and routes each alternative case to a named sibling with its selection criterion.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?