Skip to main content
Glama

sockdock_delete_rule

Destructive

Deletes a SockDock rule permanently so it stops running in Slack threads. Use sockdock_set_rule_enabled instead to pause a rule temporarily without deleting it.

Instructions

Deletes a rule. This cannot be undone, and replies in that rule's threads will get a "rule deleted" message. The user gets a notification on their Mac. To stop a rule for a while instead, use sockdock_set_rule_enabled.

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

Input Schema

NameRequiredDescriptionDefault
nameYesthe rule's name (from sockdock_list_rules)

Output Schema

NameRequiredDescriptionDefault
okYes
config_problemsNoproblems in the whole config after the change (rare)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, so the bar is lower, yet the description adds real consequences beyond them: the action is irreversible, existing thread replies receive a "rule deleted" message, and the user is notified on their Mac. These are side effects an agent could not infer from the annotations or schema and are essential before invoking a destructive tool.

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?

Three short sentences with no filler: action and irreversibility first, then concrete side effects, then the alternative. Each sentence carries distinct information.

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 destructive one-parameter tool with annotations and an output schema, the description covers irreversibility, downstream effects, notification behavior, and the safer alternative. Return values need not be explained because an output schema exists, leaving only minor gaps around scope.

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 single parameter is fully documented in the schema, including the hint that names come from sockdock_list_rules, and the description adds nothing about identifier format or lookup. With 100% schema coverage, the baseline of 3 applies.

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?

The opening sentence gives a specific verb and resource ("Deletes a rule"), which is unambiguous and immediately actionable. It doesn't itself state scope or which rules qualify, but the description as a whole separates it from the enabled/disabled sibling.

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 explicitly routes the agent to the alternative behavior: "To stop a rule for a while instead, use sockdock_set_rule_enabled," naming both the sibling and the condition that selects it. Nothing about choosing between permanent deletion and temporary disablement is left to inference.

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