Skip to main content
Glama
Sign In
DevVault MCP

DevVault MCP

by ConjureGanja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete a secret

deleteSecret

Soft-delete a secret from the vault, making it recoverable. The secret's value is never exposed.

Instructions

Soft-delete a secret (recoverable). The value is never returned.

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": "deleteSecret"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/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 discloses two important behaviors: the delete is recoverable (soft-delete) and the secret value is never returned. This goes beyond the name/title but could still mention permissions or error handling for a more complete picture.

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 two short sentences that are front-loaded with the core action. Every word adds value: the first sentence states what it does, the second adds an important behavioral constraint. There is no redundancy or fluff.

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?

The description covers the primary purpose and a key constraint, but fails to provide context on when to use it, how recovery works, or how it relates to sibling operations like rotation. Given the simple parameter set and lack of annotations, the description is minimally adequate but leaves gaps.

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 one parameter 'name' with a pattern, but no description. The tool description does not explain what 'name' refers to or any additional semantics beyond the schema's pattern. Since schema description coverage is 0%, the description needed to compensate but did not.

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 uses a specific verb 'soft-delete' and identifies the resource as 'a secret', which clearly distinguishes it from sibling tools like listSecrets, storeSecret, rotateSecret, and runWithSecrets. The parenthetical '(recoverable)' adds meaningful differentiation from a permanent delete.

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 gives no guidance on when to use this tool versus alternatives like rotateSecret or runWithSecrets. It implies deletion use, but does not state explicit conditions, prerequisites, or situations where a different operation would be more appropriate.

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