Skip to main content
Glama

解除拉黑

gwl_remove_from_blacklist
Idempotent

Removes a user from a group-class blacklist and notifies them; provide the class ID and username to unblock the user when they are currently listed.

Instructions

把一个用户移出组类黑名单(同样会通知对方)。 该用户不在名单里时返回 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": {
      "cid": "<cid>",
      "username": "<username>"
    },
    "name": "gwl_remove_from_blacklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYes组类标识(路径参数)。
usernameYes要解除拉黑的用户登录名。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior1/5

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

The description adds real behavioral detail: it notifies the affected user and specifies 404 for not-in-list and 403 for insufficient role. However, it states '重复调用不幂等' (repeated calls are not idempotent), which directly contradicts the annotation idempotentHint=true. This is a direct conflict on a property agents rely on for safe retry logic.

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?

Three short sentences, front-loaded with the action and side effect, then failure modes, then permission requirement. Every clause carries information; the parenthetical side-effect note is slightly compressed but not wasteful.

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 2-parameter mutation with an output schema, the description covers side effects, the two meaningful error codes, and the authorization prerequisite. Success-return shape is reasonably left to the output schema. The idempotency contradiction is the one deficiency in completeness.

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 both cid (path identifier with a 3-letter pattern) and username (login name, length-bounded) are already fully documented in the schema. The description adds no parameter-level meaning beyond restating that the target user is removed from the blacklist. Baseline 3 applies when the schema carries the burden.

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: '把一个用户移出组类黑名单' (remove a user from a class blacklist). That is distinct from the sibling operations add_to_blacklist and list_blacklist without naming them, because the operation is unambiguous. Sibling differentiation is implicit through the operation itself rather than explicitly stated.

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?

It gives clear preconditions for a valid call: the caller must have the class management role (class_role=owner or manage permission). It also signals the not-in-list case via the 404 return, which tells an agent not to call this for users who aren't blacklisted. It stops short of explicitly naming an alternative tool or stating when-not-to-use in prose.

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