Done Bear

List Tasks

task_list

Read-only

List tasks in the workspace, most recently updated first. Filter by view (inbox, today, upcoming, anytime, someday) and/or state (open, done, archived, all); search ranks matches within that filter. Returns up to limit tasks; hasMore is true when more matched than were returned.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`view`	No	Filter by GTD view bucket
`limit`	No	Max results
`state`	No	Filter by task state	open
`cursor`	No	Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page.
`search`	No	Ranked lexical search over title/description; when set, results are ordered by relevance instead of recency
`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

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`tasks`	Yes
`total`	Yes
`hasMore`	Yes	True when more results matched than were returned
`nextCursor`	Yes

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already mark the tool read-only and non-destructive; the description adds sorting behavior, filter semantics, search relevance ordering, and the 'hasMore' pagination signal. This is substantial behavioral context beyond the annotations with no contradiction.

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 front-loaded sentences cover the core action, sort, filters, search behavior, and pagination. There is no filler or repetition of schema defaults.

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 task listing tool with a rich output schema and fully described parameters, this description covers scope, ordering, filters, search behavior, and pagination. An agent has enough information to invoke it correctly.

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 baseline applies. The description reinforces that 'search' ranks within filters and that 'limit' bounds results, but it does not add essential per-parameter meaning beyond what the schema already documents.

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 and resource ('List tasks') with clear scope (workspace), sort order (most recently updated first), and filtering behavior. This distinguishes it from siblings like task_show, project_list, and the global search tool.

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 makes clear what task_list does and that search/filtering are internal parameters, but it never states when to prefer task_list over task_shhow or the global search sibling tool. Usage is implied rather than explicitly routed, so no exclusions or alternative guidance are present.

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

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

Need Help?