Skip to main content
Glama

sockdock_set_rule_enabled

Idempotent

Turn a SockDock rule on or off to pause it without losing its settings. A disabled rule is skipped so the next matching rule in the channel runs instead.

Instructions

Turns a rule on or off. A rule that is off is skipped, so the next matching rule in the channel runs instead; replies in its existing threads get an "off" message. Use it to pause a rule without losing its settings. The user gets a notification on their Mac.

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>",
      "enabled": "<enabled>"
    },
    "name": "sockdock_set_rule_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesthe rule's name (from sockdock_list_rules)
enabledYestrue to turn the rule on, false to turn it off

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining downstream effects: the rule is skipped, the next matching rule in the channel runs instead, existing thread replies get an "off" message, and the user is notified on their Mac. This is exactly the side-effect context an agent needs before flipping the flag.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core action and effect, then the use case, then the notification side effect. Every sentence carries information, though the opening could be slightly more compressed.

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 two-parameter toggle with a fully documented schema and an output schema, the description covers behavior, consequences, and the safe-alternative framing. Nothing an agent needs to call it correctly is missing.

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%, with both `name` (including its source, sockdock_list_rules) and `enabled` documented in the schema itself. The description adds no format or edge-case detail beyond that baseline.

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 ("Turns a rule on or off") and clarifies the operational effect — an off rule is skipped so the next matching rule runs. It implicitly contrasts with deletion ("pause a rule without losing its settings") but never names a sibling tool explicitly.

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?

"Use it to pause a rule without losing its settings" gives a clear when-to-use condition and implicitly routes away from sockdock_delete_rule. No explicit when-not guidance or named alternatives are provided.

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