Skip to main content
Glama

我提交的申请

gwl_list_my_join_requests
Read-onlyIdempotent

Lists join requests you submitted, showing pending ones by default; set handled to true to include approved, rejected, or withdrawn requests.

Instructions

列出我提交过的加入申请(裸数组)。默认只返回待处理(pending)的; handled=true 时连已批准/已拒绝/已撤回的一起返回。 每项含 group、requester_username、reviewer_username、status、already_member。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gwl_list_my_join_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
handledNotrue=同时返回已处理的申请;默认 false 只看待处理。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 bar is lower; the description still adds real value by disclosing that the result is a bare array (not an envelope) and that the default result set is filtered to pending only. It omits ordering and pagination behavior, which keeps it from a 5.

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?

Three short lines: the resource and scope first, then the default/variant behavior, then the returned fields. Every clause carries information, and the only near-redundancy is the restatement of the handled flag, which is defensible as front-loading.

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 one-parameter read tool with full annotations and an output schema, the description covers scope, default filtering, and return shape, which is sufficient to call it correctly. Minor gaps like result ordering or volume expectations are not material here.

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% and the schema already spells out that handled=true includes processed requests while false shows pending only. The description restates that same meaning rather than adding syntax or edge-case detail, so the baseline 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 states a specific verb and resource ('列出我提交过的加入申请' – list join requests I submitted), with the requester scope explicit, which separates it from manager-side listing siblings such as gwl_list_class_join_requests. It does not name or explicitly contrast any sibling, so 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?

It clearly explains the default behavior (only pending) and the condition that changes it (handled=true), which is useful selection guidance for the single parameter. However, there is no guidance on when to choose this over related tools like the class join-request listing or the cancel tool.

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