Skip to main content
Glama

Done Bear

by com.donebear

Read Guide

guide
Read-onlyIdempotent

Read Done Bear's guide for one topic: what the data means, how it relates to the rest of the product, and how to use it well. Load a topic before doing that kind of work for the first time in a session.

  • views: Placing a task in Inbox/Today/Upcoming/Anytime/Someday, reading a view, or working out why Today looks wrong.

  • dates: Setting or clearing a due date, or deciding between a deadline and a start date.

  • editing: Changing a task's fields, clearing a value, appending to notes, or moving a task between projects.

  • bulk: Completing, moving, or editing more than one task at a time, or sweeping a whole view.

  • checklists: Adding sub-steps to a task, building a list inside a task, or ticking items off.

  • comments: Discussing a task with teammates: reading its thread, replying, or correcting a comment.

  • projects: Deciding where a task belongs, creating a project or label, changing a project's status, or joining/leaving a project.

  • search: Looking a task up, listing a view, paging through results, or orienting in a new workspace.

  • workspaces: Working across multiple workspaces, hitting a permission or rate-limit error, or making retries safe.

  • agents: Starting work in a Done Bear workspace for the first time.

  • importing: The user asks how to move their tasks in from Todoist, Things, Trello or a CSV.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesGuide topic to read
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."

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
topicYes
markdownYes

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already specify readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context by clarifying that this is a prerequisite reading step and describing the guide's scope. It does not mention return values, but an output schema exists and the operation is read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, followed by a well-structured list of 11 topics with brief, concrete examples. The length is justified for disambiguating topics, and each entry is informative. It is slightly long but organized in a scannable format.

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 guide tool with complete schema coverage, explicit annotations, and an output schema, the description fully covers what the tool does, when to use it, and how to choose a topic. No critical information is missing for an agent to invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by elaborating each topic enum value with concrete usage examples (e.g., 'bulk: Completing, moving, or editing more than one task at a time'), helping the agent choose the correct topic. The context parameter is not addressed in the description, but the schema already provides detailed instructions for it.

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: 'Read Done Bear's guide for one topic' and explains what the guide contains. It is clearly distinguished from all sibling tools, which are action-oriented operations (task_add, comment_edit, etc.), whereas this tool provides guidance rather than performing product work.

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 an explicit usage trigger: 'Load a topic before doing that kind of work for the first time in a session.' The topic list further maps each guide to concrete tasks, so the agent can decide when a guide is relevant. It does not explicitly state when not to use the tool or name alternatives, but no direct alternative exists among the siblings.

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