Skip to main content
Glama

我的文档

gwl_list_my_documents
Read-onlyIdempotent

List your non-deleted documents with pagination and folder filtering: use 0 for root only, -1 for all folders, or a positive folder ID.

Instructions

列出我自己的未删除文档(分页包络)。 folder_id 默认 0(只看根目录);要一次看全部请传 -1。

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

Input Schema

NameRequiredDescriptionDefault
pageNo页码,从 1 开始。非法值由上游回落到 1,不报错。
sizeNo每页条数,1~100;超过 100 上游按 100 处理。
folder_idNo0=根目录(默认),-1=全部文件夹,正整数=指定文件夹。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful behavioral detail beyond that: results exclude deleted documents and are returned in a paginated envelope. It says nothing about ordering, ownership semantics for shared content, or empty-result behavior.

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 short sentences, with the core scope front-loaded and the folder_id branch second. Every clause carries operational information; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What remains unaddressed is the relationship to the similarly named gwl_list_documents and any note on ordering or how 'my documents' treats documents shared by others, which an agent would want before choosing between the two.

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 folder_id property already documents '0=根目录, -1=全部文件夹, 正整数=指定文件夹', so the description largely restates the schema rather than adding syntax or edge-case meaning. Page and size behavior (clamping, defaults) is documented only in the schema, which is sufficient; 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?

States a concrete verb and resource ('列出我自己的未删除文档'), plus the paginated envelope, and scopes the result to the caller's own non-deleted documents. This implicitly separates it from the broader gwl_list_documents, but it never names that sibling, so the reader must infer the distinction.

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?

Provides genuine parameter-level usage guidance for folder_id (0 = root by default, -1 = everything), which is the main decision an agent faces here. It offers no explicit tool-selection guidance, such as when to prefer this over gwl_list_documents or gwl_list_trash, leaving that to inference.

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