Skip to main content
Glama

sockdock_list_rules

Read-only

Lists all SockDock rules in execution order by channel, showing each rule's name, condition, action, status, blocking issues, and last run so you can inspect your setup or find a rule name.

Instructions

Lists every rule in the order it is tried, grouped by channel. For each rule it returns its name (use it with the other tools), channel, condition, what runs, whether it is on, why it cannot run (problem, or shadowed_by when an earlier rule in the channel always matches first), whether that channel's posts have reached SockDock since it last connected (posts_arrived: false means none yet, which only matters if someone has posted there since; absent when SockDock is not connected), and the last run. Use it to find a rule's name or to see the overall setup; for one rule's full settings use sockdock_get_rule, and to find out why one rule does not run use sockdock_check_rule.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sockdock_list_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
rulesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuine interpretation context beyond that, notably that shadowed_by means an earlier rule in the channel always matches first and that posts_arrived is absent when SockDock is not connected. Much of the enumeration restates return fields that the output schema already documents, which keeps it below a 5.

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?

Purpose and ordering constraint are front-loaded, and every clause carries information about returned fields or routing. The long run-on enumeration of returned values could be tightened or bulleted, but no sentence is pure filler.

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 zero-parameter, read-only list tool with an output schema, the description supplies what the schema cannot: ordering semantics, the shadowed_by interpretation, and the posts_arrived caveat with its connection precondition. An agent has everything needed to call it and read the result correctly.

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?

The tool takes zero parameters (schema is an empty object with additionalProperties=false), so there is no parameter meaning to add; the baseline for a no-param tool applies. The description correctly implies no input is required.

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 plus scope: 'Lists every rule in the order it is tried, grouped by channel.' It also names the sibling tools that serve adjacent purposes (sockdock_get_rule for one rule's settings, sockdock_check_rule for why a rule doesn't run), so an agent can distinguish it without opening other schemas.

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?

Gives explicit when-to-use guidance ('find a rule's name or to see the overall setup') and explicit alternatives with the condition that selects each ('for one rule's full settings use sockdock_get_rule', 'to find out why one rule does not run use sockdock_check_rule'). Nothing 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.