Skip to main content
Glama
kadenzo-mcp

kadenzo-mcp

by Kadenzo

update_dm_automation

Edit a DM automation rule to pause, resume, or update its keywords, replies, and settings. For comment_keyword rules, keep opening_message and button_label when changing other fields.

Instructions

Edit a DM automation rule — most commonly active=false/true to pause or resume it. comment_keyword rules cannot drop opening_message or button_label.

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": "update_dm_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRule id from list_dm_automations.
nameNo
activeNo
keywordsNo
ai_promptNo
ai_enabledNo
match_typeNo
button_labelNo
reply_variantsNo
opening_messageNo
once_per_user_hoursNo
public_reply_variantsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.4

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one real validation rule ('comment_keyword rules cannot drop opening_message or button_label'), which is genuinely useful and not in the schema. However, it never states whether unspecified fields are left untouched or cleared (patch vs replace) — the single most consequential behavior for a 12-parameter mutation — nor anything about permissions or the response.

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 clauses with no filler, and the primary use case is front-loaded ahead of the conditional constraint. Nothing could be removed without losing information.

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

Completeness2/5

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

For a 12-parameter mutation with no annotations, no output schema, and near-zero schema coverage, the description is far too thin. The critical missing piece is update semantics (partial vs full replacement) and the meaning of the AI/keyword matching fields, which an agent cannot safely infer before writing.

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

Parameters2/5

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

Schema description coverage is 8%: only 'id' is documented, and 11 parameters (keywords, ai_prompt, ai_enabled, match_type, reply_variants, opening_message, once_per_user_hours, public_reply_variants, etc.) have no schema text. The description explains only 'active' and touches opening_message/button_label via a constraint, leaving most parameters' meaning and interaction to be guessed from names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Edit a DM automation rule') and immediately names the dominant use case, so the agent knows this mutates an existing rule rather than creating one. It does not explicitly contrast itself with create_dm_automation or delete_dm_automation, but the name and verb make the distinction readable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Adds a concrete usage hint ('most commonly active=false/true to pause or resume it'), which tells the agent the highest-frequency call pattern. There is no guidance on when not to use it, on prerequisites (does the rule have to exist, is there a required permission), or on which sibling to prefer for other edits.

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