Skip to main content
Glama

Delete credential

delete_credential
Destructive

Delete a credential that is not in use. Refused while any cluster or running operation depends on it - check get_credential (clusters/operations) or get_github_credential_usages first. Deletion is permanent and cannot be undone.

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

Input Schema

NameRequiredDescriptionDefault
credential_idYesUUID of the credential to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description's added value is the dependency refusal rule and the explicit permanence warning ('cannot be undone'), which tells the agent the failure mode and the irreversibility before calling. It does not describe the error shape or whether a retry after clearing dependencies is safe, which would complete the 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?

Three short sentences, front-loaded with the action and its precondition, then the verification path, then the irreversibility warning. No filler and no repetition 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 one-parameter destructive tool with no output schema, the definition covers precondition, verification route, and permanence, which is most of what an agent needs. The remaining gap is what happens on refusal or success feedback, minor given the annotation coverage.

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 a single documented credential_id (UUID), so the schema already carries parameter meaning. The description adds no format, sourcing, or validation detail beyond it, which is the expected baseline when the schema does the work.

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?

States a specific verb (delete) and resource (credential) plus a scope qualifier ('not in use'), which separates it from the many other delete_* siblings operating on secrets, stacks, or clusters. An agent can identify the target object without opening the schema.

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?

Gives a concrete precondition ('Refused while any cluster or running operation depends on it') and names two prerequisite check tools, get_credential and get_github_credential_usages, with an explicit 'first' ordering. It stops short of stating what to do when the check reveals a dependency, so it is strong but not fully closed-loop.

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.