Skip to main content
Glama
Datris MCP Server

Datris MCP Server

delete_catalog

Deletes a catalog by moving all its taps and pipelines to Uncataloged, then removing only the catalog; no data is deleted, and failed moves are reported.

Instructions

Delete a catalog by moving every tap and pipeline in it to Uncataloged and removing the catalog. No tap, pipeline or data is deleted. Call this ONLY when the user has explicitly asked to delete that catalog. Uncataloged itself cannot be deleted. Items that could not be moved come back under failed (the rest still move); report them to the user. Deleting a catalog together with its items and their data is available via the API or UI, not through 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": {
      "catalog": "<catalog>"
    },
    "name": "delete_catalog"
  }
}

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.
catalogYesCatalog name to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses that items are reassigned rather than destroyed, that partial failures surface under a `failed` field while the rest still move, and that instance policy may return status `pending_approval` with an `approvalId` instead of performing the call. It also warns against re-issuing, covering the retry/idempotency hazard an agent would otherwise stumble into.

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 effect and the safety gate are front-loaded in the first two sentences, and every subsequent clause carries distinct operational information. It is dense and long, but trimming any sentence would remove a behavior (partial failure reporting, cascade-delete exclusion, or the approval loop) that an agent needs.

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?

For a two-parameter destructive tool with no annotations and no output schema, the description covers outcome, non-destruction guarantee, partial-failure handling, approval flow, and next-step tooling. An agent can execute and recover from every described state without further documentation.

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%, so both `catalog` and `reason` are already documented, including that reason is recorded in the audit log and shown to approvers. The description adds no further meaning about parameter format or matching semantics (e.g., exact name vs case sensitivity), so baseline 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 ("Delete a catalog") and precisely defines the effect: every tap and pipeline moves to Uncataloged and the catalog is removed, with no data deleted. This distinguishes it clearly from delete_tap, delete_pipeline and from a full cascade delete, which it notes is only available via API/UI.

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?

Gives an explicit gating condition ("Call this ONLY when the user has explicitly asked to delete that catalog"), an exclusion (Uncataloged itself cannot be deleted, and full cascade delete is not available here), and a full protocol for the approval path including polling get_approval, using wait_seconds, and not re-issuing the action.

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