Skip to main content
Glama

doer_delete_attachment

Delete a file attachment from a todo list by providing the todo list ID and attachment ID to remove unwanted files.

Instructions

Purge and delete a file attachment from a todo list

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": {
      "todo_list_id": "<todo_list_id>",
      "attachment_id": "<attachment_id>"
    },
    "name": "doer_delete_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
todo_list_idYesUnique identifier of the todo list
attachment_idYesUnique identifier of the attachment to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: it does not confirm the operation is irreversible, doesn't say whether the attachment blob is permanently removed or merely unlinked, doesn't cover permissions or behavior when the attachment ID is missing. Only the word 'purge' conveys destructiveness.

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 short, front-loaded sentence with no filler. 'Purge and delete' is mildly redundant since both words describe the same action, but the sentence remains efficient.

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?

For a two-parameter tool with a fully documented schema and no output schema, the essentials are present, but a destructive mutation with zero annotations deserves at least a note on irreversibility and required permissions. The definition is minimally viable rather than complete.

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 both identifiers are already documented in the input schema. The description adds no additional meaning about how todo_list_id scopes attachment_id or what happens with mismatched IDs, so it earns only the baseline.

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?

Names a specific verb ('delete'/'purge') and resource ('file attachment from a todo list'), which is enough to separate it from siblings like doer_upload_attachment and doer_list_attachments. It stops short of explicitly naming the alternative operations, but the action is unambiguous.

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?

No guidance on when this should be used versus doer_list_attachments or other removal tools, and no prerequisites (e.g., whether the attachment must first be identified via listing). 'Purge' hints at permanence, but nothing states it explicitly.

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