Skip to main content
Glama
ADIKANT

datalens-dev-mcp

by ADIKANT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dl_cleanup_apply

DestructiveIdempotent

Applies cleanup by deleting exact objects from a preview, requiring user confirmation for each delete attempt.

Instructions

Delete exact ordered objects from an unchanged preview. repeat_of asserts separate informed user authorization for one new attempt after an unknown delete; it never enables automatic retries.

Input Schema

NameRequiredDescriptionDefault
previewYes
repeat_ofNoOnly after the user accepts another possible effect: reference every unknown cleanup for these exact targets using its current store_version. Keep the originals; use a fresh preview and a new operation_id.
budget_secNo
operation_idNo
confirmed_deleteYes
max_provider_callsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.27
    • addedInput schema / properties / budget_sec
      Added value: +{
+  "default": 120,
+  "exclusiveMinimum": 0,
+  "maximum": 180,
+  "type": "number"
+}
    • addedInput schema / properties / confirmed_delete / maxItems
      Added value: +1000
    • addedInput schema / properties / max_provider_calls
      Added value: +{
+  "default": 200,
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / operation_id
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / repeat_of
      Added value: +{
+  "description": "Only after the user accepts another possible effect: reference every unknown cleanup for these exact targets using its current store_version. Keep the originals; use a fresh preview and a new operation_id.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "object_id": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "operation_id": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "receipt_version": {
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "operation_id",
+      "object_id",
+      "receipt_version"
+    ],
+    "type": "object"
+  },
+  "maxItems": 1000,
+  "type": "array",
+  "uniqueItems": true
+}
  2. Addedv1.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Against annotations that already declare destructive, idempotent, and open-world behavior, the description adds meaningful constraints: unchanged-preview requirement, repeat_of authorization rules, and no automatic retries. It does not describe permissions, rate limits, or budget effects beyond the repeat_of nuance.

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?

Two sentences, front-loaded with the core action, then a focused clarification about repeat_of. Every sentence earns its place; there is no filler or repetition.

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

Completeness2/5

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

The tool has six parameters including nested objects, low schema description coverage, and no output schema. The description gives only the core action and one behavioral nuance, leaving most parameter semantics and operational limits unaddressed.

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

Parameters2/5

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

Schema description coverage is only 17%, so the description must compensate, but it only partially explains repeat_of and implies preview's role. Other parameters such as confirmed_delete, operation_id, budget_sec, and max_provider_calls remain undocumented.

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?

The description states a specific verb and resource: 'Delete exact ordered objects from an unchanged preview.' The condition 'unchanged preview' distinguishes it from the sibling preview tool, but no sibling is explicitly named. Clear enough for an agent to understand the core action.

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?

It implies usage from an unchanged preview and gives context for repeat_of after an unknown delete, but it does not explicitly state when to use this tool instead of alternatives such as dl_cleanup_preview. No when-not conditions or alternatives are named.

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