Skip to main content
Glama
Datris MCP Server

Datris MCP Server

delete_pipeline

Delete a pipeline along with its destination data and tap ledgers. Pass keep_config=true to wipe data only and preserve the config for a clean reset.

Instructions

Delete a pipeline. This is DESTRUCTIVE: by default it removes BOTH the pipeline configuration AND all data already written to the destination (MongoDB collection rows, Postgres table rows, vector-store entries). It also wipes document-tap ledgers and staged files for any tap that targets this pipeline, so a recreate gets a clean re-ingest. The platform deliberately does NOT support deleting just the config and orphaning the data — that creates ghost state. If you want to keep the config but wipe the destination data ("reset"), pass keep_config=true; the config survives, the data does not. ALWAYS confirm with the user before calling this tool. 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": {
      "pipeline": "<pipeline>"
    },
    "name": "delete_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.
pipelineYesPipeline name to delete
keep_configNoIf true, delete only the destination data but keep the pipeline config (useful for a clean reset). Default false (full delete of both config and data).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so thoroughly: it discloses the default destructive behavior, the auxiliary artifacts destroyed, the deliberate absence of an orphan-data mode, and the exact approval-pending response contract (status `pending_approval`, `approvalId`, poll `get_approval`, use `wait_seconds`). An agent knows both the consequences and the control flow before invoking.

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?

Front-loaded with the action, then the destruction warning, then the keep_config alternative, then the approval protocol — each sentence carries distinct operational weight. The bolded DESTRUCTIVE and quoted 'reset' markers aid scanning without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema and no annotations, the description supplies the return contract for the approval path and the full consequence model of the mutation. Nothing an agent needs in order to call this safely and correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the floor; the description earns more by explaining the practical meaning of keep_config (a 'reset') and the tradeoff between config survival and data loss. The `reason` parameter is only explained in the schema, not the description, which keeps this from a 5.

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?

Uses a specific verb and resource ('Delete a pipeline') and immediately defines the blast radius: config plus destination data (MongoDB rows, Postgres rows, vector-store entries), tap ledgers, and staged files. The scope statement about not supporting config-only deletes further disambiguates this from a mere config teardown.

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 explicit operating instructions: always confirm with the user first, use keep_config=true when a data-only reset is intended, and follow the approval flow rather than re-issuing. It stops short of routing the agent to or away from sibling tools (delete_tap, delete_catalog), so sibling selection is left to inference.

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