Skip to main content
Glama

我的回收站

gwl_list_trash
Read-onlyIdempotent

Lists soft-deleted documents in pages, ordered by deletion time, to help you review and restore them.

Instructions

列出被我软删除的文档(分页包络,按删除时间倒序)。 配合 gwl_restore_document 恢复;永久删除不提供工具。

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

Input Schema

NameRequiredDescriptionDefault
pageNo页码,从 1 开始。非法值由上游回落到 1,不报错。
sizeNo每页条数,1~100;超过 100 上游按 100 处理。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

注解已经说明了安全属性(readOnly、idempotent、non-destructive),因此描述层的要求更低。描述补充了有价值的上下文:分页结构、按删除时间倒序,以及不存在硬删除路径。但它没有详细说明被删除文档是否仍然可由其他用户访问、列表是限定在每个用户还是每个文档所有者,也未说明返回条目的形态;虽然输出架构覆盖了最后一点,但描述中的这些缺口使分数为 3。

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?

两句话,没有多余内容,开头就说明列出什么、限定条件、排序和分页边界,然后说明恢复路径和缺失的硬删除。没有一句话可以删掉。

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?

对于这个简单程度而言已经具备:有注解表达安全性,有架构完整说明分页,还有输出架构,因此描述不需要解释返回结构。考虑到所谓 Recycle Bin 已有的说法,它本可以简要说明条目此前是否属于所有者或共享给他人,但除此之外已经足够。

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?

架构覆盖率达到 100%,并且包含详细的逐项描述,包括越界值的钳制行为(第 1 页回退、size 上限 100)。描述只暗示了分页,没有为参数增加任何额外含义,所以在架构承担主要工作时,基线分 3 是正确的。

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?

陈述了一个具体动作(列出)和资源(被我软删除的文档),并加上了范围限定(我自己的,即软删除的垃圾箱)与排序(按删除时间倒序)。这已足够让 agent 与同级的 gwl_list_documents 或 gwl_list_my_documents 区分开,尽管这些同级工具并未被点名。

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?

它给出了后续动作(配合 gwl_restore_document 恢复),并明确了一项限制(不提供永久删除工具),这形成了有效地何时使用与何时不能使用的指导。它没有说明什么情况下应该改用活跃文档列表工具,因此用户可能仍需要通过名称来推断这种对比。

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