Skip to main content
Glama

vault_delete

Delete one key, or the whole pocket when no key is given. Deletion is immediate and 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": {
      "vault_id": "<vault_id>",
      "secret": "<secret>"
    },
    "name": "vault_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOptional; omit to delete everything.
secretYesThe `secret` returned by vault_create, starting with `abp_`.
vault_idYesThe `vault_id` returned by vault_create. A UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / secret / description
      Added value: +"The `secret` returned by vault_create, starting with `abp_`."
    • addedInput schema / properties / vault_id / description
      Added value: +"The `vault_id` returned by vault_create. A UUID."
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does the most important thing: it states deletion is immediate and irreversible, which is the key behavioral trait for a destructive tool. It stops short of disclosing authentication/permission requirements, error behavior on a missing key or vault, or what the call returns.

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?

Two short sentences, zero filler, with the dual-mode behavior stated first and the irreversibility warning second. It is appropriately sized for a three-parameter destructive tool.

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 simple flat-schema tool with no output schema and no annotations, the description covers the essentials: what gets deleted, when the scope expands, and that the effect is permanent. The remaining gap is surrounding context such as permission requirements and post-delete state, which would push it to a 5.

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?

Schema coverage is 100%, so the schema already documents all three parameters, including 'omit to delete everything' for key. The description reinforces the key-omission semantics at the call level, which is the one parameter behavior worth repeating for a destructive tool, though it adds little beyond that.

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 (delete) and resource (one key), and states a second mode (whole pocket when no key is given). An agent can tell this apart from read/write operations. Minor terminology drift between 'pocket' and the tool's 'vault' naming slightly muddies the resource identity.

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?

It gives the condition that selects the broad-delete mode (omit key), which is genuinely useful routing information. However, there is no guidance on when to prefer this over other mutation paths, no prerequisite/permission context, and no warning about calling it without confirming which mode will trigger.

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.