Skip to main content
Glama

Delete a repository secret

remove_repo_secret
DestructiveIdempotent

Delete a named repository secret and its proxy binding. Workspace admins or owners only. Never supply a secret value.

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": {
      "workspace_id": "<workspace_id>",
      "repo_id": "<repo_id>",
      "name": "<name>"
    },
    "name": "remove_repo_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
repo_idYesThe repository id from get_workspace.
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the cascade (the proxy binding is deleted too) and the permission requirement, but says nothing about irreversibility, confirmation needs, or what is returned/errors on a missing secret.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action, then the authorization constraint, then the guardrail. No filler; slightly telegraphic but every sentence carries weight.

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?

No output schema exists, so some explanation of outcomes would help, and the description omits irreversibility and failure behavior for a destructive operation. It does cover the essentials an agent needs (identity of the resource, cascade effect, permission gate, param guardrail), so it is adequate rather than complete.

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 coverage is 67%: repo_id and workspace_id are documented in the schema, leaving only name bare. "Never supply a secret value" implicitly clarifies that name is an identifier rather than the secret material, which is useful but thin compensation for the undocumented parameter.

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 concrete verb plus resource ("Delete a named repository secret") and adds scope detail with "and its proxy binding." It is clearly distinct from listing/inspection siblings like list_repo_secrets and repo_secret_settings, though it never names an alternative explicitly.

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?

Gives a real prerequisite ("Workspace admins or owners only") and a guardrail ("Never supply a secret value"), which helps an agent decide whether it may call at all. It does not say when to prefer this over related tools such as repo_secret_settings or clear_repo_override, nor any when-not conditions.

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