Skip to main content
Glama

Delete secret

delete_secret
DestructiveIdempotent

Delete a secret and its history. Requires secrets:write and the editor role.

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": {
      "project": "<project>",
      "environment": "<environment>",
      "key": "<key>"
    },
    "name": "delete_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesSecret key, e.g. DATABASE_URL
projectYesProject slug or id
environmentYesEnvironment slug or id, e.g. development, preview or production

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not obligated to restate that this is a destructive write. It does add two pieces of value beyond the annotations: the deletion also removes the secret's history (a non-obvious, irrecoverable consequence), and the authorization prerequisites (secrets:write plus the editor role). It does not describe the response or whether dependents break.

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, front-loaded with the action and its blast radius before the permission requirements. Every clause carries information; there is no filler.

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 three-required-parameter destructive tool with no output schema and full annotation coverage, the definition supplies the crucial extras: history loss and required permissions. A note on failure modes (unknown key, missing role) or downstream impact would make it complete, but nothing essential is missing.

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%, with key, project and environment all documented including examples, so the schema carries parameter meaning. The description adds nothing further about identifying the target secret, which is acceptable at baseline but not value-adding.

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') and adds scope with 'and its history', which distinguishes it from read-only siblings like get_secret or secret_history. It stops short of explicitly naming a sibling it replaces, but the destructive action on a named resource is unambiguous.

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?

The audience and precondition are implied by the permission requirement ('Requires secrets:write and the editor role'), so an agent knows it will fail without write access. There is no explicit when-to-use versus alternatives such as set_secret (rotate) or delete_field, leaving the choice to inference.

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.

Resources