Done Bear MCP

Create Label

label_create

Create a new label in the workspace.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Label title
`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
`idempotency_key`	No	Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`ok`	Yes
`title`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 1, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered. The description adds only the workspace scope and no additional behavioral context such as duplicate handling, side effects, or restrictions, but it does not contradict the annotations.

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 a single, clear sentence with no filler. It front-loads the action and the resource and is appropriately sized for a simple label-creation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given full schema coverage, an output schema, and annotations, the description is minimally sufficient for invoking the tool. It lacks routing guidance versus label_add and does not mention any labeling constraints, leaving a small but notable gap.

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 already documents both required parameters fully. The description adds no parameter-level meaning beyond what the schema provides, which is the expected baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Create') and names a clear resource ('a new label') with workspace scope, so an agent can understand the core action. It does not, however, distinguish itself from the sibling tool label_add, which may overlap in intent.

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

Usage Guidelines2/5

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

The description provides no guidance about when to prefer this tool over label_add, label_list, or label_remove, nor any prerequisites or uniqueness constraints. The appropriate usage is only weakly implied by the word 'Create'.

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

Disambiguation4/5

Task operations are clearly separated into distinct actions, and the resource tools (attachment, checklist, comment, project) are each tied to a specific object. The main ambiguity is between search and task_list, since task_list accepts a search parameter; descriptions help, but an agent could still misselect.

Naming Consistency3/5

Task tools follow a consistent task_verb pattern, but other tools mix bare nouns with an action parameter (attachment, checklist, comment, project), use reversed noun_verb (label_create), or are bare verbs/nouns (search, guide). The set is readable but not uniformly patterned.

Tool Count5/5

15 tools is within the well-scoped range for a task-management server, and each tool covers a distinct area: task lifecycle, search, context, projects, labels, attachments, checklists, comments, and guidance. No tool feels redundant or gratuitous.

Completeness4/5

The task lifecycle is well covered: create, show, list, edit, complete, reopen, and archive. Minor gaps include no permanent task deletion, no label update/delete tool, and no project removal, but these are workable and do not block core workflows.

Resources

Need Help?