Skip to main content
Glama
RawTree MCP Server

RawTree MCP Server

Official
by rawtreedb

Delete Workflow

delete-workflow
DestructiveIdempotent

Delete a workflow definition and its schedule, stopping future evaluations. Does not undo previous SQL writes or completed deliveries. Returns { id, deleted: true } only after the API confirms deletion.

Instructions

Delete a workflow definition and its schedule, stopping future evaluations. Does not undo previous SQL writes or completed deliveries. Returns { id, deleted: true } only after the API confirms deletion. Requires an admin API key bound to the selected organization and cluster, or OAuth. Organization members may read; organization admins may create, update, or delete. Workflows execute with organization credentials and continue after the creating key is revoked or expires.

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": {
      "organization": "<organization>",
      "cluster": "<cluster>",
      "id": "<id>"
    },
    "name": "delete-workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWorkflow ID returned by list-workflows, get-workflow, or create-workflow.
clusterYesRawTree cluster to use for this operation.
organizationYesRawTree organization containing the target cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.2

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing non-reversibility scope ("does not undo previous SQL writes or completed deliveries"), the exact success shape ({ id, deleted: true }) and the fact it is only returned after API confirmation, plus credential binding and workflow execution semantics. This is the kind of context annotations cannot carry.

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?

Purpose and irreversibility caveat are front-loaded, and the return-value contract is placed well. The final sentence about workflows running under organization credentials and surviving key revocation is tangential to performing a delete, so a sentence does not fully earn its place.

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?

With no output schema present, the description supplies the return contract itself, along with side effects, authorization prerequisites, and scope limits. For a three-parameter destructive tool this covers everything an agent needs before invoking.

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%, so the schema already documents id, cluster, and organization; baseline 3 applies. The description adds a small amount by implying why organization and cluster are required (the admin key must be bound to them), but it adds no syntax, format, or ID-sourcing detail beyond the schema.

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 workflow definition and its schedule") plus the operational consequence ("stopping future evaluations"), which cleanly separates it from delete-saved-query, delete-table, and the sibling workflow tools (get-workflow, update-workflow). An agent needs no schema lookups to know what this removes.

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 clear authorization context (admin API key bound to the org/cluster, or OAuth) and the role model, which tells the agent when the call is permitted. It does not explicitly say what to use instead when the intent is to temporarily stop evaluations (e.g., update-workflow) rather than remove the definition, so there is no exclusion guidance.

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