Skip to main content
Glama

审批加入申请

gwl_review_join_request

Approve or reject a pending group join request by ID, with an optional note. Approving creates membership only and requires owner or manage permission for the group class.

Instructions

批准或拒绝一条加入申请:approve=true 批准入组,false 拒绝。 批准只是建立成员关系,不会因此提权。 已处理过的再审批 409;目标用户在黑名单里 409;申请不存在 404。需要该组类的管理角色(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": {
      "request_id": "<request_id>"
    },
    "name": "gwl_review_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo备注 / 附言(最多 200 个字符,上游超限返回 400)。
approveNotrue=批准入组,false=拒绝。默认 true。
request_idYes申请 id(路径参数)。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the permission prerequisite (class_role=owner or manage permission, else 403), the specific 409/404 failure modes, and the important side-effect boundary that approval only creates membership without granting elevated privileges. These are exactly the facts an agent needs before mutating state and are consistent with readOnlyHint=false and idempotentHint=false.

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 action and the approve flag before the caveats, and no sentence is filler. The telegraphic error-code list is dense but efficient; a short structural marker separating preconditions from failure modes would improve it slightly.

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 return values need not be explained; within that division of labor the description covers the action, its non-obvious side effect, the authorization requirement, and the failure modes. Nothing an agent needs to invoke this correctly is missing.

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 all three parameters (request_id, approve, note) are already documented in structured data and the baseline applies. The description restates the approve boolean rather than adding new meaning, and never mentions the note parameter or its 200-character limit, 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 names a concrete verb pair and resource ('批准或拒绝一条加入申请') and immediately pins the discriminating flag semantics (approve=true 批准, false 拒绝), so the agent knows exactly what action is performed. It does not explicitly distinguish itself from related siblings such as gwl_cancel_join_request or gwl_list_class_join_requests, which is why it falls short of a 5.

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 by the error taxonomy (already-processed → 409, blacklisted user → 409, missing request → 404, insufficient role → 403), which tells the agent when the call is valid. However, it never names an alternative tool or states when NOT to use this one (e.g. to withdraw your own request, use cancel_join_request; to find a request_id, use list_class_join_requests), leaving routing to inference.

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