Skip to main content
Glama

撤回我的申请

gwl_cancel_join_request
DestructiveIdempotent

Withdraw your own pending join request by request_id to mark it cancelled; retrieve the ID with gwl_list_my_join_requests. Approved or rejected requests cannot be withdrawn.

Instructions

撤回我自己提交的加入申请,状态变为 cancelled。 只能撤自己的(否则 403);已被批准或拒绝过的再撤回会 409。 先用 gwl_list_my_join_requests 取 request_id。

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": {
      "request_id": "<request_id>"
    },
    "name": "gwl_cancel_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes申请 id(路径参数)。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's added value is the state transition (变为 cancelled) and the concrete failure semantics (403 for others' requests, 409 for already-decided ones). It does not say whether a cancellation can be undone or what happens to the class membership afterwards, which is the remaining gap for a destructive mutation.

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 sentences, front-loaded with the action and state change, then constraints, then the prerequisite. No filler and nothing repeated from the title or schema.

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 one-parameter mutation with an output schema already present, the description covers the action, the resulting state, the authorization boundary, the conflict case, and how to source the id. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single request_id parameter, so the baseline is 3; the description earns above baseline by telling the agent where to obtain a valid request_id (gwl_list_my_join_requests) rather than leaving it to guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (撤回加入申请) plus the resulting state (cancelled) and the scope restriction (只能撤自己的). An agent can distinguish this from gwl_review_join_request or gwl_list_my_join_requests without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit prerequisite (先用 gwl_list_my_join_requests 取 request_id) and names the two conditions under which the call must not be made (别人的申请 → 403;已批准/已拒绝 → 409). This is when-to-use, when-not-to-use, and the alternative source of the required id in three sentences.

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