Skip to main content
Glama

Remove attachment

remove_attachment
Destructive

Remove an attachment from a draft, event, or contact you own by specifying its attachment ID, so you can update the item before sending or sharing.

Instructions

Remove an attachment from a draft (or from an event/contact you own).

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

Input Schema

NameRequiredDescriptionDefault
attachmentIdYesAttachment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive mutation. The description adds one useful piece of context beyond that: the ownership constraint and the draft case. It does not say whether the removal is permanent, whether it affects the underlying file, or what happens if the ID is unknown.

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?

One sentence, front-loaded with the action and resource, with the scope qualifier in parentheses. No redundant restatement of the title and nothing that could be cut without losing information.

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, single-parameter mutation with no output schema, the definition covers what is removed and from where. It is thin on consequences: irreversibility, error cases for invalid/non-owned attachment IDs, and whether the attachment must be re-uploaded to restore it are all unstated.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents attachmentId. The description adds no format, source, or validation meaning beyond that, which is the expected baseline for a one-parameter tool with a fully described schema.

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 names a specific verb and resource (remove an attachment) and bounds the scope to drafts and owned events/contacts. That is enough to separate it from siblings like add_attachment or list_attachments, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the parenthetical scope: you remove from a draft or from an event/contact you own. There is no explicit when-not guidance (e.g., use download_attachment to fetch, add_attachment to attach) and no statement of prerequisites such as required permissions.

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