Skip to main content
Glama
Datris MCP Server

Datris MCP Server

delete_tap

Deletes a tap and its stored script, returning pending_approval with an approvalId when policy requires approval; poll get_approval instead of re-issuing the action.

Instructions

Delete a tap and its stored script. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the tap 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 well: it discloses the asynchronous approval outcome (`pending_approval` plus `approvalId`), the user-facing message to relay, and the non-idempotent warning against retrying. What it omits is whether the deletion is permanent or recoverable (a `restore_tap_version` sibling exists) and any permission or lifecycle preconditions such as stopping a running tap.

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?

The destructive action is front-loaded in the first clause and the approval mechanics follow in a single dense sentence with no filler. Slightly long for a two-parameter delete, but every clause carries operational meaning.

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 mutation tool with no annotations and no output schema, the description covers the critical failure mode (approval gating) and the recovery path thoroughly. It is still short on irreversibility and error conditions (unknown tap name, insufficient permission), which is the remaining gap.

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 already declare their meaning, including that `reason` lands in the audit log and is visible to approvers. The description adds no new syntax, format, or naming constraints 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?

States a specific verb and resource plus the scope of the deletion ('a tap and its stored script'), so the agent knows exactly what is removed rather than assuming only the tap record. The distinction from a secret-only deletion is implicit but the object 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 Guidelines5/5

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

Explicitly explains the branch where the call does not execute (person-approval policy) and names the follow-up tools: poll `get_approval` with the returned id, pause via `wait_seconds` between polls, and do not re-issue. This is a complete when/how-to-proceed instruction rather than a vague pointer.

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