Skip to main content
Glama
Sign In
Skool MCP Server

Skool MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Decline membership request

decline_membership_request
Destructive

Decline a pending applicant’s request to join a Skool group; use the request ID from pending membership requests. Admin and moderator access only.

Instructions

Decline an applicant's request to join.

Declines one pending request, as Skool's Decline button does. Admins and moderators only.

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>",
      "request_id": "<request_id>"
    },
    "name": "decline_membership_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
request_idYesrequest_id from list_membership_requests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the tool destructive, non-read-only, non-idempotent, and open-world. The description usefully adds the admin/moderator permission constraint and clarifies that it acts on exactly one pending request, though it does not explain downstream effects such as applicant notification.

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?

The description is short and front-loaded with the action. The second sentence slightly restates the first by repeating 'Decline,' but it also adds useful scope and permission information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, admin-only mutation with no output schema, the description covers the core action and permissions. It still leaves out what a successful decline does to the applicant or request beyond the destructive annotation, so it is adequate but not fully complete.

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%, so both parameters are already documented in the schema. The description adds little parameter-level meaning beyond indicating that request_id refers to a single pending request, which is consistent with the schema's reference to list_membership_requests.

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 description states a specific verb and resource: declining an applicant's request to join. It is clearly distinct from sibling approve_membership_request and list_membership_requests by operation, though it does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It specifies that the tool declines one pending request and is limited to admins and moderators. However, it does not explicitly compare usage against approve_membership_request, remove_member, or ban_member, so the when-to-use guidance is only implied.

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

Deploy Server

Other Tools