Skip to main content
Glama
kadenzo-mcp

kadenzo-mcp

by Kadenzo

delete_dm_automation

Permanently deletes a direct-message automation rule by ID. Use it to remove unwanted DM workflows; set the rule inactive instead if you may want to restore it later.

Instructions

Delete a DM automation rule permanently. Prefer update_dm_automation with active=false if the user may want it back.

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": {
      "id": "<id>"
    },
    "name": "delete_dm_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.4

TDQS

A4.4/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 behavioral burden, and it delivers the single most important fact for a mutation: the deletion is permanent. It does not cover permission requirements, whether dependent rules/keywords are also removed, or whether a confirmation is expected, which keeps it below 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?

Two short sentences with zero filler: the destructive action is stated first and the safer alternative follows. Every sentence earns its place and the warning is front-loaded.

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 with no output schema, the description supplies what the agent actually needs: the action, its permanence, and the safer alternative. Remaining omissions (id format, cascade effects, auth) are minor but non-zero.

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 0% and the sole parameter ('id') is undocumented in the schema, so the description must compensate. It implies the id identifies the DM automation rule but adds no format, source (e.g., from list_dm_automations), or validation detail, leaving a modest gap for an otherwise obvious parameter.

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?

The description uses a specific verb and resource ('Delete a DM automation rule') and immediately qualifies the scope with 'permanently,' so an agent knows exactly what object is affected and that the effect is irreversible. It also implicitly distinguishes itself from the update sibling by framing deletion as the hard option.

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?

It names the concrete alternative (update_dm_automation with active=false) and states the condition that selects it ('if the user may want it back'). That is explicit when-to-use-this-vs-that guidance rather than an inference the agent has to make.

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