Skip to main content
Glama

我的组类清单

gwl_list_my_classes
Read-onlyIdempotent

Lists all organizations and groups you joined or own in one flat result, including IDs, roles, ownership, and readiness status so you can locate a class ID (cid).

Instructions

平铺返回我加入或拥有的所有组类(组织 + 组),是找 cid 的入口。 每项含 id(3 位字母)、name、kind(organization/group)、org_id、owner、role、is_active、is_public、node、can_manage。 另带 status{tables_ready, missing, hint}:组织数据表未就绪时 hint 会说明原因。

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_my_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare that the tool is read-only, idempotent, open-world, and non-destructive, so the description does not need to restate safety. It usefully adds one degradation behavior that the annotations do not cover: the status{tables_ready, missing, hint} block, in which hint explains why org tables are not ready. It also discloses that the output is flat, which affects how the caller must traverse it. The field enumeration overlaps with the output schema, so the score falls short of 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?

The description is front-loaded with the core action and scope in the first clause, then the caller's purpose, then the payload shape. It is efficiently sized for the information amount. The enumerated field list (id, name, kind, org_id, owner, role, is_active, is_public, node, can_manage) largely duplicates the output schema, which is the main word that does not fully earn its place.

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?

The tool takes zero parameters, has a full output schema, and has annotations that cover the safety profile. Even so, the description supplies the missing behavioral nuance about how the status block degrades when org tables are not ready. Nothing material is left for an agent to guess before invoking it.

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, so the schema has no parameter semantics to document; the baseline for zero parameters is 4. The description spends none of its words on inputs, and the only arguable input-like content is the implicit absence of filtering, which is stated as 'flat return' and 'all classes I joined or own'.

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?

The description gives an exact verb and resource: it returns all classes (organizations + groups) that the user has joined or owns, and it explicitly states the result is flat rather than nested. The scope qualifier '\u6211\u52a0\u5165\u6216\u62e5\u6709' (joined or owned) implicitly separates this tool from a discovery-oriented sibling such as gwl_list_joinable_classes, and the stated role as the entry point for finding a cid makes the tool's identity unmistakable.

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?

The phrase '\u662f\u627e cid \u7684\u5165\u53e3' (it is the entry point for finding a cid) gives a clear trigger for when to use the tool. However, the description never names any alternative or states when NOT to use this tool. For example, it never contrasts the tool with listing joinable classes or listing orgs. The guidance is therefore solid but not explicit.

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