Skip to main content
Glama
kelleyblackmore

Vault MCP Server

vault_delete

Delete a secret from HashiCorp Vault at a specified path to remove sensitive data and maintain security.

Instructions

Delete a secret from Vault at the specified path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesThe path to delete the secret from (e.g., 'secret/data/myapp')

Implementation Reference

  • Handler implementation for the vault_delete tool. Extracts the path from arguments, calls vaultClient.delete(path), and returns a success message.
    case "vault_delete": {
      const { path } = args as { path: string };
      await vaultClient.delete(path);
      return {
        content: [
          {
            type: "text",
            text: `Successfully deleted secret at path: ${path}`,
          },
        ],
      };
    }
  • src/index.ts:77-90 (registration)
    Registration of the vault_delete tool in the TOOLS array, defining its name, description, and input schema requiring a 'path' string.
    {
      name: "vault_delete",
      description: "Delete a secret from Vault at the specified path",
      inputSchema: {
        type: "object",
        properties: {
          path: {
            type: "string",
            description: "The path to delete the secret from (e.g., 'secret/data/myapp')",
          },
        },
        required: ["path"],
      },
    },
  • Input schema for vault_delete tool, specifying an object with required 'path' property of type string.
    inputSchema: {
      type: "object",
      properties: {
        path: {
          type: "string",
          description: "The path to delete the secret from (e.g., 'secret/data/myapp')",
        },
      },
      required: ["path"],
    },
Behavior2/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 states the tool deletes a secret, implying a destructive mutation, but doesn't mention critical aspects like whether deletion is permanent, requires specific permissions, has side effects (e.g., affecting other paths), or what happens on success/failure. This leaves significant 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with zero waste—it states the action, resource, and key input concisely. It's front-loaded and efficiently communicates the core purpose without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., permanence, permissions), expected outcomes, or error handling. Given the complexity and risk of deletion, more context is needed to guide safe and effective use.

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?

The schema description coverage is 100%, with the single parameter 'path' fully documented in the schema (including an example). The description adds no additional meaning beyond the schema's details, such as path format constraints or deletion scope. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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') and resource ('a secret from Vault'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like vault_list or vault_write, which would require mentioning it removes data rather than listing or creating it.

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?

The description provides no guidance on when to use this tool versus alternatives like vault_list or vault_write. It lacks context about prerequisites (e.g., needing an existing secret) or exclusions (e.g., not for reading data), leaving the agent to infer usage from the tool name alone.

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/kelleyblackmore/vault-mcp'

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