Skip to main content
Glama

Typebar (formerly SuperDocs)

delete_attachment

Removes the attachment from the session; the AI will no longer reference it in subsequent chat turns. If processing is still in progress, also cancels the underlying job. Use to free up context, remove sensitive files mid-session, or replace a stale reference document. The attachment_id can be either the final attachment ID or the job ID (during processing).

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": {
      "attachment_id": "<attachment_id>",
      "session_id": "<session_id>"
    },
    "name": "delete_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
attachment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing that the AI will stop referencing the attachment and that an in-progress job will be canceled. However, it does not state whether deletion is permanent or recoverable, what permissions or auth are required, or what happens on invalid IDs, leaving meaningful behavioral gaps for a destructive operation.

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 description is four efficient sentences with the core purpose front-loaded, followed by side effect, usage contexts, and parameter flexibility. Every sentence adds relevant information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool with no annotations or output schema, the description covers purpose, side effects, usage, and the ambiguous ID semantics. It is nearly complete but omits session_id meaning, error behavior, and explicit permanence/auth details.

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 0%, so the description must compensate. It does add important semantics for attachment_id by allowing either the final attachment ID or the job ID during processing, but it does not explain session_id beyond what its name implies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: it removes an attachment from a session and clarifies that the AI will no longer reference it. It also distinguishes the tool from a pure job-cancellation operation by explaining that deletion cancels an in-progress job as a side effect.

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

Usage Guidelines4/5

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

The description gives clear usage contexts: free up context, remove sensitive files mid-session, or replace a stale reference document. It does not explicitly say when to use cancel_job instead or when deletion is inappropriate, so it falls short of full alternatives/exclusions 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.