Skip to main content
Glama

组类黑名单

gwl_list_blacklist
Read-onlyIdempotent

List blacklisted users for a class or organization, including user ID, username, reason, creator, and timestamp; organization IDs aggregate blacklists from subordinate groups.

Instructions

列出该组类的黑名单(裸数组:user_id、username、reason、created_by、created_at)。 传组织 id 时汇总下辖组。需要该组类的管理角色(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_blacklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYes组类或组织标识(路径参数)。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses the authorization gate (403 without owner/manage) and the org-id aggregation semantics, which the agent cannot get from structured fields. The returned field list is somewhat redundant given an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the return shape first, then the org-id and permission caveats. Nothing is padded and the key constraint is easy to find.

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?

For a single-parameter read-only listing tool with annotations and an output schema, the description covers everything that matters: return shape, org aggregation behavior, and required permissions.

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 coverage is 100% and cid is already documented there, so the schema carries most of the weight. The description does add real meaning by clarifying that cid may be an org identifier and that this changes the result set to include subordinate groups.

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 concrete verb and resource ('列出该组类的黑名单') and adds scope detail (org-id aggregation of subordinate groups). It is unambiguous next to the add/remove blacklist siblings, though it never names an alternative explicitly.

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 a prerequisite (must be class_role=owner or hold manage, otherwise 403) and explains the alternate behavior when an org id is passed. It stops short of saying when to prefer a different listing tool or what to do on failure.

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