Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Add group rule

add_group_rule
Destructive

Add a rule at the end of the group rules. Admins only. Adds a rule after the existing ones, as Settings, Rules, Add does, and returns the whole new list. Nobody is notified and it is undone with delete_group_rule, so it runs without asking first.

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": {
      "group": "<group>",
      "title": "<title>"
    },
    "name": "add_group_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
titleYesRule title, up to 30 characters.
descriptionNoWhat the rule means, shown under the title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and openWorldHint=true, so the bar is met, and the description still adds real signal: append-only ordering, the full list is returned, no one is notified, and 'runs without asking first' explicitly tells the agent no confirmation prompt is expected. The undo path via delete_group_rule reconciles destructiveHint with reversibility rather than contradicting it.

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?

Front-loaded with purpose and packed with useful context in a few clauses. There is mild redundancy between 'at the end of the group rules' and 'after the existing ones', and the UI analogy adds length without new information.

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?

No output schema exists, and the description compensates by stating that the whole new rule list is returned. Combined with the admin gate, notification behavior and undo path, everything needed to call this correctly and anticipate its effects is present.

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 description coverage is 100% with per-field documentation for group, title (including the 30-char limit) and description, so the schema carries parameter meaning. The description adds nothing about parameter format or constraints, which is acceptable at this coverage level but is baseline only.

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+resource plus positional semantics ('at the end of the group rules', 'after the existing ones'), which cleanly separates it from update_group_rule and delete_group_rule. The 'Settings, Rules, Add' analogy pins the exact user-facing operation.

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 hard prerequisite ('Admins only') and names the inverse operation ('undone with delete_group_rule'), so an agent knows the entry and exit points. It stops short of saying when to prefer update_group_rule over adding a new rule when a similar rule already exists.

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

All Skool MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources