Skip to main content
Glama

Delete secret

delete_secret
Destructive

Delete an organisation secret and its stored value. Refused while any live resource still uses it; the refusal names those resources, which must stop using the sentinel first. The value is not recoverable. Needs the secrets.manage permission (organisation owners and admins).

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

NameRequiredDescriptionDefault
nameYesThe secret's name as list_secrets shows it, or its ${SECRET_SLOT:<id>} sentinel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered; the description then adds behaviour the annotations cannot convey. It discloses that the delete can be blocked, that the blocked response enumerates the offending resources, that the caller must detach the sentinel before retrying, that the value is unrecoverable, and which permission/role set is required. That is a rich set of non-obvious traits and nothing conflicts with the annotations.

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?

Four short sentences, front-loaded with the action, then the refusal condition, then irreversibility, then authorisation. Every sentence carries distinct information an agent would otherwise have to discover by failing a call, and there is no redundant restatement of the title.

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 single-parameter destructive tool with no output schema, the description covers the gaps that matter: blocking preconditions, the shape of a refusal, irreversibility and permissions. It does not mention whether deleting a non-existent name errors silently or loudly, which matters slightly given idempotentHint=false, but the definition is otherwise complete enough to call safely.

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?

With one parameter at 100% schema description coverage, the schema already explains that 'name' accepts either the displayed name or the ${SECRET_SLOT:<id>} sentinel. The description only echoes the sentinel concept indirectly in the refusal sentence and adds no matching, format or ambiguity guidance beyond the schema. Baseline 3 applies.

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 opens with a specific verb and scoped resource: 'Delete an organisation secret and its stored value.' The 'organisation' qualifier separates it from sibling deletion tools such as delete_application_env_secret, delete_organisation_variable and delete_credential, and the phrase 'and its stored value' states that the underlying data goes too, not just the metadata entry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear preconditions rather than a bare when-to-use line: deletion is 'refused while any live resource still uses it', the callers blocking it are identified by the refusal, and they must be reconfigured first. It also names the required permission. It stops short of pointing at an alternative operation (e.g. rotate_secret when the intent is replacement rather than removal), so the routing to a sibling is implied rather than explicit.

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.