Skip to main content
Glama
Datris MCP Server

Datris MCP Server

delete_tap_secret

Delete an agent-created tap secret to clean up after the tap is no longer needed. Only secrets tagged _type=tap are removed; human-owned secrets must be deleted from the Secrets tab.

Instructions

Delete a tap secret. Only secrets created by an agent (tagged _type=tap) can be deleted via this tool; secrets owned by a human user must be removed from the Secrets tab. Use this to clean up after a tap is no longer needed. If this Datris instance's agent policy requires a person to approve this action, the call does NOT perform it: it returns status pending_approval with an approvalId. Tell the user it is waiting for approval in Datris, then poll get_approval with that id (pause with wait_seconds between polls) — do not re-issue the action.

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_tap_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap secret to delete.
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses the ownership restriction, the possible non-execution path returning pending_approval plus approvalId, and the polling workflow. The remaining gap is failure and reversibility semantics — it never says whether the deletion is permanent or what it returns when the secret is missing or not agent-owned.

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?

Core action and ownership constraint are front-loaded, and the approval flow follows in a coherent order with no filler. The approval paragraph is dense but every sentence carries operational information an agent must act on.

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 two-parameter mutation tool with no output schema, the definition covers the safety-critical pieces: ownership gating, the pending_approval response shape, and the polling sequence. It falls short only on success/failure outcomes and irreversibility, which matter for a destructive operation.

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 100% and both parameters are documented there, including the audit-log purpose of reason. The description adds no format, constraints, or naming conventions beyond the schema, so the baseline of 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 resource ('Delete a tap secret') and immediately narrows scope to agent-created secrets tagged _type=tap, so an agent can tell it apart from update_secret or list_tap_secrets without opening a schema.

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

Usage Guidelines5/5

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

It states when to use it ('clean up after a tap is no longer needed') and when not to (human-owned secrets must be removed from the Secrets tab), and it spells out the approval-required branch with the exact follow-up calls (get_approval, wait_seconds) and the instruction not to re-issue.

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

Deploy Server

Other Tools