Skip to main content
Glama
Sign In
homebox-mcp

homebox-mcp

by dgahagan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_attachment

Destructive

Permanently remove an attachment from an item or location by providing its ID and confirming the exact title. Prevents accidental deletion by requiring confirmation.

Instructions

PERMANENTLY delete one attachment from an item or location (see list_attachments for ids). confirm must equal the attachment's exact title.

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

Input Schema

NameRequiredDescriptionDefault
confirmYes
identifierYes
attachment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds behavioral context beyond the destructiveHint annotation by emphasizing 'PERMANENTLY' and the confirmation requirement. This discloses the irreversibility and safety mechanism.

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 a single concise sentence with a key note, front-loaded with the action and no wasted words.

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

Completeness5/5

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

For a simple delete operation with three required parameters, the description covers purpose, prerequisites, and confirmation requirements. The absence of an output schema is acceptable as delete operations typically return minimal results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description explains the confirm parameter explicitly and hints at attachment_id/identifier via the list_attachments reference and 'from an item or location' context.

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 clearly states the tool's purpose: 'PERMANENTLY delete one attachment from an item or location'. It uses a specific verb and resource, and distinguishes from sibling tools like rename_attachment and get_attachment.

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?

It provides usage guidance by referencing list_attachments to obtain IDs and requiring exact title confirmation. It doesn't explicitly mention exclusions or alternatives, but the context is clear.

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

Deploy Server

Other Tools