Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

delete_attachment

Destructive

Permanently removes an attachment from a note and deletes the file from the server; this action cannot be undone.

Instructions

Permanently delete an attachment from a note (the file is removed from the server; this cannot be undone).

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": {
      "noteId": "<noteId>",
      "attachmentId": "<attachmentId>"
    },
    "name": "delete_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYes
attachmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is established. The description adds meaningful behavioral detail beyond that: the file is removed from the server and the action is irreversible. It does not describe permission requirements or what happens to note references, keeping it from a 5.

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?

The definition is a single, front-loaded sentence with no wasted wording. The parenthetical adds high-value irreversibility and server-removal context rather than restating the tool name.

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 destructive two-parameter mutation, the description covers the critical irreversibility warning and server-side effect. However, with no output schema and no parameter documentation, it leaves gaps around identifier sourcing, permissions, and failure behavior.

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?

There are two required parameters with 0% schema description coverage, so the description must compensate for the missing documentation. It mentions deleting 'from a note' and an 'attachment,' which loosely maps to noteId and attachmentId, but it provides no format, source, or lookup guidance for either identifier.

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 states a specific verb and resource: 'Permanently delete an attachment from a note.' It clearly identifies the target resource and distinguishes itself from non-destructive attachment siblings like add_attachment and get_attachment, though it does not explicitly name alternatives.

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?

The description says the deletion is permanent and cannot be undone, which is useful context, but it provides no guidance on when to use this tool versus alternatives such as trashing a note or leaving the attachment in place. There are no prerequisites or exclusion conditions stated.

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