Skip to main content
Glama
Upload-Post

Upload-Post

Official

Delete an AutoDM rule

delete_autodm_rule
Destructive

Permanently remove an AutoDM rule, including its stats and queued DMs, when you need irreversible cleanup. Use pause instead to temporarily stop a rule.

Instructions

Permanently delete an account-wide AutoDM rule with its stats and queued DMs. Cannot be undone; use pause_autodm_rule for a break.

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": {
      "rule_id": "<rule_id>"
    },
    "name": "delete_autodm_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYesAutoDM rule ID (`rule_id` from list_autodm_rules or create_autodm_rule).

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.23.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description earns credit for adding specifics beyond that: the stats and queued DMs are destroyed and the action is irreversible. It stops short of covering permission requirements or what happens to in-flight DMs.

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, both front-loaded: consequence first, then the alternative. No filler.

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 single-parameter destructive tool with an output schema and annotations covering safety, the description supplies the missing pieces: what is destroyed, irreversibility, and the safer alternative.

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 rule_id parameter is fully described in the schema, including its source tools. The description adds no parameter-level meaning, which is the correct baseline here.

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), resource (account-wide AutoDM rule), and even the collateral (stats and queued DMs). It distinguishes the scope from the similarly named delete_autodm sibling by specifying 'account-wide AutoDM rule'.

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?

Explicitly names pause_autodm_rule as the alternative for a temporary break, which tells the agent when not to use this tool. It does not address the delete_autodm sibling or any prerequisites, leaving a small gap.

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