Done Bear MCP

List Labels

label_list

Read-only

List labels in the workspace. Returns up to limit labels; hasMore is true when more matched than were returned.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results; the response's `hasMore` reports truncation
`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."
`workspace`	No	Workspace id, slug, or name

Output Schema

TableJSON Schema

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

TDQS

A4.1/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 clear. The description adds useful behavioral context beyond annotations: results are capped by `limit` and `hasMore` indicates truncation. This helps the agent understand pagination behavior without relying solely on schema.

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?

The description is two concise sentences with no filler. The core action appears first, followed by the only non-obvious operational detail about pagination. Every sentence contributes information.

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?

Given a simple read-only list tool, rich annotations, a fully described schema, and an existing output schema, nothing essential is missing. The workspace scope, limit behavior, and truncation indicator are communicated. The agent has enough to successfully call and interpret the tool.

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 documents all parameters: `limit`, `context`, and `workspace`. The description's mention of `limit` and `hasMore` largely duplicates the `limit` property description rather than adding new meaning. It does not enrich `workspace` or `context` semantics.

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 verb is explicit and specific: 'List labels' in the workspace. It clearly distinguishes from sibling label operations like label_add, label_create, and label_remove because those are mutation tools, not listing tools. The purpose is immediately actionable.

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 implicitly signals when to use this tool: when the agent needs to enumerate labels in a workspace. However, it does not explicitly mention alternatives or state when not to use it, such as when searching or when needing label details from labels. No exclusions are provided.

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

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

Most tools are cleanly separated by resource and action, and each family (checklist, comment, label, project, task) follows the same shape. The main blur is between search and task_list's optional search filter, and convenience tools like checklist_done overlap with checklist_edit.

Naming Consistency4/5

The dominant convention is snake_case noun_verb (task_add, checklist_list, comment_remove), with consistent verb families across resources. A few outliers like get_context, search, and guide break the pattern, but overall the naming is predictable and readable.

Tool Count2/5

At 35 tools, this is a heavy surface for a task-management server and exceeds the 25-tool threshold. Several tools are convenience variants (task_done vs task_bulk_done, checklist_done vs checklist_edit) that could be consolidated or represented as parameters.

Completeness4/5

The core task lifecycle is well covered: create, show, edit, complete, reopen, archive, list, assign, and bulk operations, with full checklist and comment CRUD. Notable gaps are label deletion/renaming, project deletion, and search being limited to tasks, but these are minor for the apparent product scope.

Resources

Need Help?