aarifmms/keyblind

Overview Schema Source Related Servers Discussions Admin

delete_secret

Permanently remove a named secret from the encrypted vault so it can no longer be resolved at runtime. Use it to revoke credentials or clean up unused keys.

Instructions

Delete a secret from the vault.

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

Input Schema

Name	Required	Description
`exp`	No	Expiry epoch seconds bound into the signature (required with agentId)
`name`	Yes	The name of the secret to delete
`nonce`	No	Single-use nonce bound into the signature (required with agentId)
`token`	No	Org-issued short-lived access token (alternative to agentId)
`agentId`	No	Agent ID for signed, scope-enforced access (optional)
`signature`	No	Ed25519 signature over 'write:<name>:<nonce>:<exp>' in base64 (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.9.2Oct 27, 2026

addedInput schema / properties / agentId

Added value: +{
+  "description": "Agent ID for signed, scope-enforced access (optional)",
+  "type": "string"
+}

addedInput schema / properties / exp

Added value: +{
+  "description": "Expiry epoch seconds bound into the signature (required with agentId)",
+  "type": "number"
+}

addedInput schema / properties / nonce

Added value: +{
+  "description": "Single-use nonce bound into the signature (required with agentId)",
+  "type": "string"
+}

addedInput schema / properties / signature

Added value: +{
+  "description": "Ed25519 signature over 'write:<name>:<nonce>:<exp>' in base64 (optional)",
+  "type": "string"
+}

addedInput schema / properties / token

Added value: +{
+  "description": "Org-issued short-lived access token (alternative to agentId)",
+  "type": "string"
+}

First observedv0.1.4May 27, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden and fails to disclose that deletion is presumably irreversible, that authentication is required via token or agentId+signature scheme, or what happens if the named secret does not exist. The only behavior stated is the bare mutation itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but it is undersized for a six-parameter, auth-gated destructive operation. Brevity here reads as under-specification rather than efficiency.

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 with six parameters, a signed-access auth scheme, no annotations, and no output schema, one sentence is far from sufficient. An agent gets no warning about permanence, auth requirements, or error behavior.

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?

Schema description coverage is 100%, so all six parameters (including the signature/nonce/exp auth scheme) are already documented in the schema. The description adds nothing about the 'name' parameter or the auth alternatives, so the baseline 3 applies.

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?

States a specific verb and resource: 'Delete a secret from the vault.' An agent can tell it apart from store_secret and resolve_secret without opening schemas, though it says nothing about scope or whether deletion is permanent.

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?

There is no when-to-use guidance, no mention of prerequisites, and no reference to siblings such as list_secrets (to identify the name) or resolve_secret. The agent must infer everything about context.

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