Skip to main content
Glama

加入组类

gwl_join_class

Join a group class by ID; public groups join directly, while private groups submit an access request. Idempotent, returning already_member=true for existing members.

Instructions

加入组类:public 组直接入组(data.mode=joined),private 组转为提交申请(data.mode=requested)。 已经是成员不会报错,会回 already_member=true(幂等)。 失败语义:组已停用 / 非公开且不允许申请 / 我在黑名单 403;cid 非法 400。message 最多 200 个字符。

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": {
      "cid": "<cid>"
    },
    "name": "gwl_join_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYes要加入的组类标识(路径参数)。
roleNo入组角色名:字母开头,可含数字与下划线,1~32 个字符。默认 member。member
messageNo申请附言(private 组会给审批人看),最多 200 个字符。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Adds substantive behavior beyond the annotations: the two outcome modes, the already_member=true no-error path, and concrete failure semantics (disabled group / non-public without requests / blacklisted → 403, invalid cid → 400). This is exactly the kind of disclosure a mutation tool needs. Minor tension worth noting: the description calls the already-member case idempotent while the annotation says idempotentHint=false, which is reconcilable if only that one path is de-duplicated, but the description does not say so.

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 the outcome modes, then the idempotent path, then the failure taxonomy — a sensible priority order for a mutating call. Dense but readable. The trailing 'message 最多 200 个字符' is redundant with the schema and could be dropped.

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?

For a three-parameter mutation with annotations covering safety, an output schema, and full schema coverage, the description supplies the missing pieces: dual outcome semantics and error conditions. It lacks any mention of authentication or permission prerequisites (e.g. whether joining requires being in the org), which would fully close the loop.

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 the schema already explains cid, role, and message. The only parameter detail the description repeats is the 200-character message limit, which duplicates maxLength. It says nothing about what the role parameter means for the membership being created, so it adds little beyond the schema.

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 (joining a group class) and immediately splits the outcome by group visibility: public groups yield data.mode=joined, private groups yield data.mode=requested. That is far more specific than the title. It does not name a sibling to contrast with (e.g. gwl_cancel_join_request or gwl_list_joinable_classes), so it stops short of full sibling differentiation.

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?

Usage context is implied rather than stated: the reader infers this is the tool for becoming a member of a class, and that private groups go through an approval flow. There is no explicit 'use this instead of X when…' routing, and no pointer to the tool that lists joinable classes or to the one that cancels a request, which are the natural next steps.

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