Skip to main content
Glama

可加入的公开组

gwl_list_joinable_classes
Read-onlyIdempotent

Lists public groups that allow self-service joining, optionally filtered by a three-letter class ID to narrow results to one organization; invalid class IDs return a 400 error.

Instructions

列出所有允许自助加入的 public 组(返回裸数组,上限 200 条)。 class_id 可收窄到某个组织下的组;传了不属于任何组织的 id 会 400。

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

Input Schema

NameRequiredDescriptionDefault
class_idNo可选:只看某个组织/组类下的可加入组(3 位字母)。省略=全部公开组。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, yet the description still adds genuinely new behavior: the result is a bare array capped at 200 entries, and an invalid class_id that matches no organization returns a 400. The 200-entry truncation is exactly the kind of caveat an agent cannot obtain from annotations, and it signals that results may be incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences state scope first, then return shape and the class_id refinement with its error case. There is no filler, and the most important qualifier (joinable public groups) is front-loaded.

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?

An output schema exists, so the return values need no prose. For a single-optional-parameter list tool, the description covers scope, result shape and truncation limit, parameter refinement, and the error condition, which is everything needed to call it 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?

Schema coverage is 100%, so the baseline would be 3, but the description goes beyond the schema by naming the failure mode of class_id: a 3-letter id belonging to no organization yields a 400 rather than an empty list. That addition changes how an agent should interpret an error.

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 concrete verb and resource: list all public groups that permit self-service joining. That scope ('joinable') distinguishes it in substance from the sibling tools gwl_list_my_classes, but no sibling is named, so the agent must infer the boundary itself.

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 explains one usage lever, namely that class_id narrows the result to one organization. It never says when to choose this tool instead of gwl_list_my_classes, gwl_get_class, or gwl_list_class_join_requests, and gives no exclusion to cover the 'all public groups' default.

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