Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

ds_raw_delete

Send a raw DELETE request to DolphinScheduler API endpoints not handled by dedicated delete tools; use it for uncovered endpoints because deletes are irreversible.

Instructions

Send a raw DELETE request to the DolphinScheduler API (escape hatch).

Deletes are irreversible. Prefer the dedicated ds_delete_* tools; use this only for endpoints they do not cover.

Args: path: API path starting with / and excluding the /dolphinscheduler prefix, with any query string, e.g. "/projects/123/schedules/7"

Returns: DolphinScheduler's response as-is ({"code", "msg", "data", ...}); code 0 means success.

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": {
      "path": "<path>"
    },
    "name": "ds_raw_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.8/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 warns that deletes are irreversible, explains the path convention including the excluded /dolphinscheduler prefix, and documents the response envelope with 'code 0 means success'. It stops short of stating auth/permission requirements or whether a failed delete is partially applied, which keeps it from a 5.

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?

The warning and routing rule are front-loaded, then Args and Returns sections carry the detail. Every sentence adds information; nothing is restated from the schema.

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 one-parameter destructive tool with no annotations and no output schema, the definition covers purpose, alternative routing, path format, irreversibility, and return-value interpretation. An agent has everything needed to call it correctly.

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

Parameters5/5

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

Schema coverage is 0% for the single path parameter, so the description must compensate and does: it specifies the leading slash, the excluded prefix, that a query string may be included, and gives a concrete example path.

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?

Names a specific verb and resource ('Send a raw DELETE request to the DolphinScheduler API') and labels itself an escape hatch, which cleanly separates it from ds_raw_get/post/put and the curated ds_delete_* tools.

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?

Explicit routing guidance: prefer the dedicated ds_delete_* tools and use this one only for endpoints they do not cover. Both the when and the when-not are stated, along with the tradeoff (irreversibility) that motivates the preference.

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