Skip to main content
Glama

Done Bear

by com.donebear

Show Task Details

task_show
Read-only

Get full details for a single task including its labels and checklist items. Pass its workspace-scoped task number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesWorkspace-scoped task number, encoded as a string
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."
timezoneNoIANA 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.
workspaceNoWorkspace id, slug, or name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYes
labelsYes
checklistItemsYes

TDQS

A4/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, covering the safety profile. The description adds useful behavioral context by specifying that the result includes labels and checklist items and that the caller must pass a workspace-scoped task number rather than a global ID.

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 short sentences with no filler. The core action and output scope are front-loaded, followed immediately by the key invocation instruction.

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?

With read-only annotations, 100% schema coverage, and an output schema present, the description is largely complete for invoking the tool correctly. It does not explicitly mention the workspace or context parameters, but those are fully described 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 all four parameters are documented in the schema. The description only reinforces the task-number requirement and does not add substantive meaning beyond the schema, 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?

States a specific verb and resource: 'Get full details for a single task', and names distinguishing output content (labels and checklist items). It clearly reads as a detail-view tool distinct from listing or search siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies when to use the tool (when full details of a single task are needed), but it does not explicitly compare against alternatives like task_list or search, nor does it state when not to use it. Usage is left somewhat to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Done Bear toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Tools are grouped cleanly by resource (task, checklist, comment, label, project, attachment), so most actions have an obvious owner. The main ambiguities are task_list vs. search and checklist_done vs. checklist_edit, but the descriptions call out the intended boundaries clearly enough to avoid frequent misselection.

Naming Consistency4/5

The dominant resource_verb pattern (task_add, task_edit, checklist_list, comment_remove, project_join) is consistent and predictable. A few outliers like get_context, guide, search, and task_attachment_list break the pattern, but the naming remains readable and mostly uniform.

Tool Count2/5

At 35 tools, this is a very large surface for an agent to choose from and exceeds the 25-tool threshold where count becomes a liability. The tools are well organized, but the repeated verb families across six resources make the total feel heavy even though each tool is plausibly justified.

Completeness4/5

The core task lifecycle is well covered: create, show, edit, list, complete, reopen, archive, assign, and bulk operations, plus full checklist, comment, label, and attachment workflows. Notable gaps are the lack of an explicit unarchive/restore path and no label edit/delete, but these are minor enough that agents can usually work around them.

Resources