Skip to main content
Glama
Upload-Post

Upload-Post

Official

Pause an AutoDM rule

pause_autodm_rule
Idempotent

Pause an account-wide AutoDM rule to stop outgoing DMs until it is resumed; existing settings and stats remain intact.

Instructions

Pause an account-wide AutoDM rule: it sends no DMs until resume_autodm_rule. Its settings and stats are kept.

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": "pause_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?

Beyond the annotations, the description explains the concrete effect: no DMs are sent until resume_autodm_rule is called. It also states that settings and stats are retained, which meaningfully clarifies that the operation is non-destructive and reversible.

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?

The definition is a single front-loaded sentence with no unnecessary wording. It communicates scope, effect, and retention efficiently.

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 one-parameter pause operation with rich annotations and an output schema, the description supplies everything an agent needs: what is paused, what stops happening, how to resume, and what is retained.

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?

The sole parameter rule_id is fully documented in the schema, including its source from list_autodm_rules or create_autodm_rule. The description does not add parameter meaning beyond that, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: pause an account-wide AutoDM rule. It also immediately clarifies the operational effect, sending no DMs until resumed, which distinguishes this from a generic pause.

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?

The description gives clear context by naming resume_autodm_rule as the inverse action and explaining that pausing preserves settings and stats. It does not explicitly state when to choose this over other pause variants, but the intended temporary-stop use case is clear.

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