Skip to main content
Glama

Coline

Read a task's attachments

read_task_attachments
Read-onlyIdempotent

Lists what is attached to a task to show the work (change requests, Code sessions, emails, messages, files, recordings, links, notes), each with its state, and the latest finish by an agent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>"
    },
    "name": "read_task_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
finishYes
attachmentsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds useful shape about the response (each attachment carries its state, plus the latest agent finish), but says nothing about pagination, ordering, empty results, or permission requirements beyond what annotations and the output schema already convey.

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?

A single front-loaded sentence with the verb and resource first and the detail in a parenthetical list; nothing is padded or repeated. The dense enumeration is slightly list-like but each item earns its place by telling the agent what to expect back.

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?

The tool is a simple three-parameter read with full annotation coverage and an output schema, so return-value detail is rightly omitted. However, two of three required parameters are undocumented in both schema and description, leaving a real gap for an agent that does not already know how to resolve taskboardId and taskId.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: only 'workspace' is documented in the schema, while taskId and taskboardId have no descriptions anywhere. The description supplies no parameter meaning at all, so an agent gets no help on how to obtain or format the task and taskboard identifiers.

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 ('Lists') with a clear resource ('what is attached to a task') and enumerates the attachment categories (change requests, Code sessions, emails, files, links, notes), so an agent knows exactly what comes back. It is distinguishable from mutating siblings like attach_to_task and remove_task_attachment, but it never names a read-side alternative such as read_task_history or read_task_state.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of how this differs from sibling read tools on the same task (history, state, view, relations). The agent must infer that this tool is for inspecting attachments rather than task state, which is implied but never stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources