Skip to main content
Glama
Sign In
vaultshell

vaultshell

by SoWhatI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

secret_delete

Delete a stored secret from the backend and remove its rules.yaml registration to stop it being injected into shell sessions.

Instructions

Delete a secret from the backend and unregister it from rules.yaml.

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": {
      "name": "<name>"
    },
    "name": "secret_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses a non-obvious side effect—unregistering from rules.yaml—but omits other critical behavioral context such as whether deletion is permanent, what permissions are required, or what happens if the secret is in active use.

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, front-loaded sentence that efficiently conveys the core action and an important side effect with no wasted words.

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

Completeness3/5

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

For a simple one-parameter delete tool with no annotations or output schema, the description covers the action and side effect but leaves significant gaps: no parameter details, no warning about irreversibility or permissions, and no return information.

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 schema has zero description coverage for the single 'name' parameter. The description does not compensate by explaining what the name represents (e.g., its format, source, or relation to rules.yaml), leaving the agent without guidance beyond the basic type.

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 (Delete) and resource (a secret), and adds the side effect of unregistering from rules.yaml. This clearly distinguishes it from siblings like secret_set (create/update), secret_list, and secret_probe, which serve different operations.

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 explicit guidance on when to use this tool versus alternatives, when not to use it, or any prerequisites. It merely states what the tool does, leaving usage entirely to inference from the name.

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