Skip to main content
Glama

组收到的申请

gwl_list_class_join_requests
Read-onlyIdempotent

Lists join requests for a class or organization, filtered by status (pending by default). Use it to review membership applications; requires owner or manage permission.

Instructions

列出某组类收到的加入申请(裸数组,需管理权限)。 传组织 id 会汇总其下辖组的申请。status 默认 pending,可取 all / approved / rejected。需要该组类的管理角色(class_role=owner 或权限含 manage),否则 403。

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

Input Schema

NameRequiredDescriptionDefault
cidYes组类或组织标识(路径参数)。
statusNo筛选申请状态。默认 pending(待处理);all 返回全部历史。pending

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the read-only and idempotent annotations, the description discloses that the result is a bare array (no pagination or wrapper object), that the authorization requirement is a class-level manage role and failures return HTTP 403, and that passing an organization id broadens the scope to sub-groups. These are real behavioral facts that an agent cannot learn from the annotations.

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 three short sentences, and it puts the scope and permission constraint first. It somewhat repeats the status enum and default that the schema already documents, so a little content is redundant, but it is still tight overall.

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?

Given a two-parameter, read-only listing tool that has an output schema, the description covers scope, permission requirements, and the status filter well enough for the agent to call it correctly. The only minor gap is that it does not mention behavioral alternatives, but none is strictly needed for correct invocation.

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 score is 3; the description still adds meaning by explaining that cid may be an org identifier, which triggers aggregation of subordinate groups' requests, and it restates the status enum values and the pending default. The aggregation semantics go beyond the schema's terse '组类或组织标识'.

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 uses the specific verb '列出' (list) and the resource '某组类收到的加入申请' (join requests received by a class), which an agent can easily distinguish from the sibling tool gwl_list_my_join_requests. The sibling tools are not named explicitly, so an agent must infer the distinction from the wording rather than from explicit guidance, although the wording is still clear.

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 gives permission prerequisites (owner or manage role, otherwise 403) and notes that passing an org id aggregates its sub-groups. However, it does not state when to use this tool instead of the related tools, such as reviewing via gwl_review_join_request or viewing one's own requests via gwl_list_my_join_requests; that usage 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.