Skip to main content
Glama

Coline

Remove an attachment

remove_task_attachment

Takes one attachment off a task. History keeps that it was there.

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>",
      "attachmentId": "<attachmentId>"
    },
    "name": "remove_task_attachment"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
removedYes

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 destructiveHint=false, idempotentHint=false and deviation from a naive "delete" expectation, and "History keeps that it was there" usefully explains the soft-removal semantics that justify the non-destructive hint. However, the description says nothing about what happens on a second call (relevant given idempotentHint=false), nor about auth or failure when the attachment is missing.

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 short sentences, front-loaded with the action and its scope; no redundant wording. It leans toward under-specification rather than verbosity, so it is efficient but thin.

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 described, but for a mutating three-parameter tool with two undocumented parameters the text leaves real gaps around identifier semantics and repeat-call behavior. The single behavioral note about history is valuable but not sufficient on its own.

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%: workspace is documented inline, but taskboardId and attachmentId have no schema descriptions. The description adds no meaning beyond "one attachment" – it does not clarify what attachmentId refers to, whether the taskboardId is the owning board, or what form the identifiers take.

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?

"Takes one attachment off a task" gives a specific verb (remove) and resource (task attachment) with an explicit cardinality constraint ("one"), which cleanly separates it from read_task_attachments or attach_to_task without naming them.

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 explicit when-to-use guidance, no mention of the alternative attach_to_task/read_task_attachments path, and no prerequisites (permissions, whether the task must be open). The agent must infer the usage context from the verb alone.

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