Skip to main content
Glama

组的加入状态

gwl_get_join_info
Read-onlyIdempotent

Checks a class group's visibility and your membership status—public, joinable, member, blacklisted, and pending join request—so you can decide whether to apply before joining.

Instructions

查询某组类的可见性与「我」的状态:is_public、joinable、is_member、blacklisted、request(我提交的待处理申请,没有则 null)。 这条不需要组类身份,任何人都能先探测再决定要不要申请加入。

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: no class-level identity/authorization is needed, and `request` is null when there is no pending application, which clarifies an otherwise ambiguous return field. It still says nothing about behavior for an unknown or malformed class id, so it is good but not rich.

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 sentences: the first lists the returned state fields, and the second front-loads the no-authorization constraint and the intended use. Nothing is redundant or padded.

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?

The tool is a read-only, single-parameter lookup with full annotations and an output schema, so the description need not explain return values; it nevertheless names the key fields. Completeness is high, with only minor gaps around error or not-found behavior.

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?

There is a single parameter, and the schema already documents it fully (path parameter, pattern ^[A-Za-z]{3}$, with a description) at 100% coverage. The description adds no extra syntax or format detail for `cid`, so the baseline of 3 applies.

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 a specific verb and resource (query a class's join/visibility state) and enumerates the exact fields returned: is_public, joinable, is_member, blacklisted, request. That field list distinguishes it from siblings such as gwl_join_class (performs the join) and gwl_list_my_join_requests (lists requests broadly). It does not name any sibling explicitly, which keeps it just 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 Guidelines4/5

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

The sentence 'anyone can probe first before deciding whether to apply' establishes a clear usage moment, namely checking joinability before applying. It does not state exclusions or name the alternative tool to call in order to actually join or to list requests, so the routing guidance is contextual but not explicit.

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