Skip to main content
Glama

sockdock_reorder_rules

Idempotent

Reorder a Slack channel's SockDock rules so the first enabled match runs, letting specific rules take priority over broad ones that would otherwise hide them.

Instructions

Sets the order of one channel's rules; the first is tried first, and the first enabled rule that matches a post runs. List every rule of that channel exactly once (names from sockdock_list_rules). Use it when a broad rule (such as all_posts) is above a specific one and hides it. 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": {
      "channel": "<channel>",
      "names": "<names>"
    },
    "name": "sockdock_reorder_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesevery rule of the channel once, in the new order
channelYeschannel name (#dev-help or dev-help) or ID; must be in sockdock_list_channels

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.3/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, and closed-world behavior. The description adds real context beyond that: how rule evaluation proceeds (first enabled matching rule wins), the strict requirement to list every rule exactly once, and the user-visible side effect of a Mac notification. What is missing is the consequence of an incomplete names list (silent removal, error, or reordering).

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?

Three sentences, front-loaded with the core ordering rule and evaluation behavior, followed by the operational constraint and side effect. The notification sentence is slightly tangential but is disclosed behavior rather than filler.

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?

With an output schema present, return values need no explanation, and the description covers purpose, semantics, constraints, and side effects for a two-parameter write operation. The one remaining hole is behavior on invalid or incomplete name lists.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema does not: that order equals evaluation priority and that names must come from sockdock_list_rules. This clarifies the semantics of the 'names' array beyond its schema text.

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 and resource ('Sets the order of one channel's rules') and immediately defines the ordering semantics that make the operation meaningful. It is clearly distinct from siblings like sockdock_set_rule_enabled and sockdock_save_rule, which do not control evaluation priority.

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?

Gives a concrete triggering scenario ('when a broad rule such as all_posts is above a specific one and hides it'), which tells the agent exactly when to reach for this tool. It also points to sockdock_list_rules as the source of names. It stops short of naming an explicit when-not case, so it is strong but not complete.

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