Skip to main content
Glama

Coline

Attach to a task

attach_to_task

Attaches one thing that shows the work on a task: a change request, a Code session, a message, an email thread, a Drive file (doc, recording, screenshot), a crew run, a commit, a link or a short note. Coline reads its title and state from the real thing.

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>",
      "attachment": "<attachment>"
    },
    "name": "attach_to_task"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
idYes
hrefYes
kindYes
refIdYes
titleYes
checksYes
addedByYes
previewYes
summaryYes
finishIdYes
canRemoveYes
createdAtYes
stateLineYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the mutation profile is covered. The sentence "Coline reads its title and state from the real thing" adds real, non-obvious behavior — attachment metadata is derived from the source object rather than supplied — but it is phrased vaguely and says nothing about duplicate attachments, permissions, or idempotency despite idempotentHint=false.

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?

Two sentences, front-loaded with the action and scope, no filler. The trailing metadata sentence is slightly cryptic ("the real thing") and could be sharper, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the attachment variants are enumerated. For a four-required-param mutation tool with sparse schema coverage, though, the description leaves open where IDs come from, what happens on re-attach, and the task-vs-event distinction.

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 only 25%, so the description must carry weight; it does list the nine attachment kinds in prose, aiding the oneOf selection pressure. However, it adds no meaning beyond the schema's const discriminators (e.g. that email requires a threadId plus optional accountId, or that commit needs a sha), and says nothing about workspace, taskboardId or taskId.

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?

States a specific verb and resource ("Attaches one thing ... on a task") and enumerates the concrete artifact types, so the agent knows exactly what this tool does. It implicitly scopes to tasks rather than events, which separates it from attach_to_event, but never names that sibling explicitly.

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 statement of when to use this tool versus attach_to_event or remove_task_attachment, and no prerequisites such as where taskId/taskboardId come from. The list of attachable kinds helps the caller pick an attachment variant, but that is parameter choice, not tool-selection guidance.

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