Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Discover groups

discover_groups
Read-onlyIdempotent

Search Skool's public directory of communities, with members, price and rating. Searches skool.com/discovery, the public list of communities, as its search box does: URL name, title, description, member count, price and review rating. 30 to a page; pass next_cursor back as cursor. Private groups that hide from discovery are not listed.

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": "discover_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords to look for. Left out: the top groups.
cursorNoNext page cursor from the previous call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent operation, and the description adds useful behavior beyond that: pagination size (30 per page), cursor reuse, and the fields returned. It does not discuss rate limits or ordering, but the key behavioral traits for a read-only discovery tool are covered.

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 front-loaded with the core purpose and stays compact. It packs in search scope, returned fields, pagination and exclusions without obvious repetition, though it is a dense sentence cluster rather than crisply structured bullet-like guidance.

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?

There is no output schema, so the description usefully names the result fields and explains pagination. It also states the discovery-surface scope and exclusion of hidden private groups, leaving only minor gaps such as result ordering and authentication expectations.

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%, and both parameters already have descriptions, including that omitting query returns top groups. The description adds the page size and cursor mechanics, but most parameter meaning is already in the schema, so this is baseline territory.

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: searching Skool's public directory of communities, with fields like members, price and rating. The 'public directory' scope clearly separates it in spirit from list_groups or search_group, though it never names those siblings 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?

Gives clear context for use: discovering public communities via skool.com/discovery, as the site's search box does. It also notes that private groups hiding from discovery are not listed, which clarifies result scope, but it does not explicitly route the agent away from list_groups or search_group as alternatives.

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