Done Bear MCP

Show Task Details

task_show

Read-only

Get full details for a single task: its fields, labels and checklist items, by workspace-scoped task number. Add include for the parts that cost extra reads: ["comments"] for the discussion thread (oldest first, with author and whether each was edited) and ["attachments"] for the files on it, each with a short-lived signed URL.

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."
`include`	No	Extra sections to load. Omit unless you need them: each is its own round trip
`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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`task`	Yes
`labels`	Yes
`comments`	No
`attachments`	No
`checklistItems`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 5, 2026

addedOutput schema / properties / task / properties / completedAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Completion instant in UTC (ISO 8601), or null for an unfinished task"
+}

changedOutput schema / properties / task / required

Previous value: -[
-  "assigneeId",
-  "completed",
-  "deadline",
-  "description",
-  "id",
-  "number",
-  "projectId",
-  "startDate",
-  "state",
-  "teamId",
-  "title",
-  "view"
-]New value: +[
+  "assigneeId",
+  "completed",
+  "completedAt",
+  "deadline",
+  "description",
+  "id",
+  "number",
+  "projectId",
+  "startDate",
+  "state",
+  "teamId",
+  "title",
+  "view"
+]

Changed5 schema fields changedSep 4, 2026

addedInput schema / properties / include

Added value: +{
+  "description": "Extra sections to load. Omit unless you need them: each is its own round trip",
+  "items": {
+    "enum": [
+      "comments",
+      "attachments"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / attachments

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "filename": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "mediaType": {
+        "type": "string"
+      },
+      "sizeBytes": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "filename",
+      "id",
+      "mediaType",
+      "sizeBytes",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / comments

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "author": {
+        "description": "Display name of the member who wrote it",
+        "type": "string"
+      },
+      "authorId": {
+        "type": "string"
+      },
+      "body": {
+        "type": "string"
+      },
+      "createdAt": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "ISO 8601 instant"
+      },
+      "edited": {
+        "description": "True when the body has been changed since it was posted",
+        "type": "boolean"
+      },
+      "id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "author",
+      "authorId",
+      "body",
+      "createdAt",
+      "edited",
+      "id"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / task / properties / completed

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The date (YYYY-MM-DD) the task was completed, in the requested timezone. Null while it is still open"
+}

changedOutput schema / properties / task / required

Previous value: -[
-  "assigneeId",
-  "deadline",
-  "description",
-  "id",
-  "number",
-  "projectId",
-  "startDate",
-  "state",
-  "teamId",
-  "title",
-  "view"
-]New value: +[
+  "assigneeId",
+  "completed",
+  "deadline",
+  "description",
+  "id",
+  "number",
+  "projectId",
+  "startDate",
+  "state",
+  "teamId",
+  "title",
+  "view"
+]

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The description adds valuable behavior beyond that: comments come oldest first with author and edit status, attachments each include a short-lived signed URL, and optional sections are extra round trips.

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 carry substantial information with no filler. The main purpose is front-loaded first, and the include details are efficiently placed in the second sentence.

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?

For a read-only detail tool with a rich output schema and fully described parameters, the description is complete. It covers scope, optional sections, and their behavioral characteristics; nothing needed for correct invocation is missing.

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 schema already documents the parameters. The description enhances the 'include' parameter specifically by explaining what each value returns and the extra-read cost, which is meaning beyond the schema's generic description.

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 full details') and resource ('a single task') and enumerates what is included: fields, labels, and checklist items. It distinguishes itself from list-oriented siblings by emphasizing it targets one workspace-scoped task number.

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 guidance on when to add the 'include' parameter: only for comments or attachments that cost extra reads, with 'Omit unless you need them' reinforcing restraint. It does not explicitly name sibling alternatives like task_list, but the single-task scope is clear enough for an agent to route correctly.

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

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?