Spaces by Peakflo

workflow_delete

Destructive

Permanently delete a workflow, including its versions and triggers. This cannot be undone: confirm the workflow name with the user first.

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": {
      "workflowId": "<workflowId>"
    },
    "name": "workflow_delete"
  }
}

Input Schema

Name	Required	Description	Default
`workflowId`	Yes	The workflow ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real substance beyond them: the deletion cascades to versions and triggers, it is permanent, and it is irreversible. What is still missing is whether dependent executions or references break, but the key danger facts are disclosed.

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 permanence and cascade behavior, then immediately the confirmation requirement. No filler.

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

Completeness4/5

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

For a single-parameter destructive tool whose annotations already carry the safety profile, this covers action, scope, irreversibility, and a pre-call safeguard. Nothing critical is missing; a note on post-delete effects on related executions would make it fully complete.

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% and the single workflowId parameter is documented in the schema, so baseline 3 applies. The description's mention of confirming the workflow name adds a mild safety hint but does not clarify the ID format, source, or whether a name would be accepted instead.

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 ("Permanently delete") and resource ("a workflow"), and clarifies the blast radius ("including its versions and triggers"), which distinguishes it from the sibling delete-node, delete-edge, and delete-version tools.

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 an explicit operational precondition: confirm the workflow name with the user before calling. It does not however name an alternative for the narrower case (e.g., workflow_delete_node or workflow_delete_edge), so an agent must infer that this is whole-workflow removal only.

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

All Spaces by Peakflo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.