Skip to main content
Glama

Delete Attachment

keychain_delete_attachment

Remove files from vault items to manage storage and maintain organized password management systems.

Instructions

Delete an attachment from an item. Returns the updated (redacted) item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes
attachmentIdYes
revealNo

Implementation Reference

  • Implementation of the keychain_delete_attachment tool handler in src/tools/registerTools.ts.
      `${deps.toolPrefix}.delete_attachment`,
      {
        title: 'Delete Attachment',
        description:
          'Delete an attachment from an item. Returns the updated (redacted) item.',
        inputSchema: {
          itemId: z.string(),
          attachmentId: z.string(),
          reveal: z.boolean().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const item = await sdk.deleteAttachment(clampReveal(input));
        return {
          structuredContent: { item },
          content: [{ type: 'text', text: 'Deleted.' }],
        };
      },
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a destructive operation ('Delete') and mentions the return value ('updated (redacted) item'), which adds some context. However, it lacks details on permissions, error conditions, or what 'redacted' entails, leaving gaps for a mutation tool.

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?

The description is brief and front-loaded with the core action, consisting of two sentences that efficiently convey the purpose and outcome. There's no unnecessary verbiage, making it easy to parse, though it could benefit from more detail given the complexity.

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

Completeness2/5

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

For a destructive tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't cover parameter meanings, error handling, or the implications of deletion (e.g., permanence), leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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?

The input schema has 0% description coverage for its 3 parameters (itemId, attachmentId, reveal), and the description provides no additional semantic information about them. It doesn't explain what 'reveal' does or how to obtain the IDs, failing to compensate for the schema's lack of documentation.

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 clearly states the action ('Delete an attachment') and target resource ('from an item'), which is specific and unambiguous. It distinguishes from siblings like 'keychain_delete_item' by focusing on attachments rather than entire items. However, it doesn't explicitly differentiate from 'keychain_get_attachment' in terms of operation type.

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 is provided on when to use this tool versus alternatives like 'keychain_delete_item' or 'keychain_delete_items'. The description doesn't mention prerequisites, such as needing the item and attachment IDs, nor does it clarify the relationship with sibling tools like 'keychain_create_attachment'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/icoretech/warden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server