Done Bear

List Task Attachments

task_attachment_list

Read-only

List the files attached to a task, each with a short-lived signed URL to read it. Only attachments that finished uploading are included.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	Yes	Workspace-scoped task number, encoded as a string
`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
`items`	Yes
`total`	Yes
`taskId`	Yes
`hasMore`	Yes	True when more results matched than were returned

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds valuable behavioral details beyond those annotations: URLs are short-lived signed URLs, and attachments still uploading are excluded. This is exactly the kind of extra context an agent needs.

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 tightly written sentences, no fluff, with the core action front-loaded and the behavioral caveats placed right after. Every sentence earns its place.

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 list operation with a present output schema and fully documented parameters, the description covers the non-obvious behavioral caveats (signed URL expiry, upload completion filter). Nothing essential is missing.

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 all three parameters. The tool description does not add parameter-specific meaning, but given full schema coverage, a baseline of 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?

Description uses an explicit verb ('List') and resource ('files attached to a task'), and clarifies each item carries a short-lived signed URL. This clearly distinguishes it from sibling tools like task_attach and task_attachment_remove.

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 makes the use case clear—listing completed attachments for a task—and implies this is the read counterpart to task_attach and task_attachment_remove. It does not explicitly name alternatives or exclusions, but the context is strong enough for an agent to select it appropriately.

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?