Skip to main content
Glama

组类详情

gwl_get_class
Read-onlyIdempotent

Retrieve detailed information about a specific group class, including ID, name, kind, owner, role, permissions, and management capabilities. Use it to verify membership access and permissions.

Instructions

读取某个组类的详细信息:id、name、kind、org_id、owner、role、can_manage、permissions[]、permission_map。 仅成员、owner、上级组织管理方或超管可见;不是成员 403,不存在 404,cid 不是 3 位字母 400。

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context the annotations do not carry: authorization requirements and the specific HTTP-style error semantics (403/404/400). It omits return format and pagination, which is acceptable since 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 dense sentences, no filler: returned fields first, then access/error conditions. Front-loaded and every clause carries information an agent can act on.

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 single-parameter read tool with full annotations and an output schema, the definition covers purpose, access, and failure modes completely enough to invoke correctly. The only missing piece is how to obtain a valid cid (which sibling lists it), a minor gap.

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?

With a single parameter at 100% schema coverage, the schema already documents the cid path parameter and its ^[A-Za-z]{3}$ pattern. The description's only added meaning is restating the constraint as a 400 error condition, which is marginal over 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 ('读取某个组类的详细信息') and enumerates the returned fields (id, name, kind, org_id, owner, role, can_manage, permissions[], permission_map), so an agent knows exactly what it gets. It does not name a sibling alternative (e.g. list_my_classes to discover a cid), so it falls 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear access conditions — only members, the owner, parent-org managers, or superadmins may call it — and states the failure conditions (403 non-member, 404 missing, 400 malformed cid). It stops short of explicit when-to-use-vs-alternative routing, but the caller preconditions are unambiguous.

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