Skip to main content
Glama

文件夹列表

gwl_list_folders
Read-onlyIdempotent

Lists folders only (no documents) with IDs, names, scope, hierarchy, and metadata. Filter by scope or parent ID to get all visible folders, root-level items, or direct children.

Instructions

只列文件夹(不含文档),返回裸数组:id、name、scope、user_id、group_name、parent_id、sort_order、is_active、created_at、updated_at;group 范围的项还带 class_id/org_id/group_root。 scope 省略时返回我全部可见的文件夹;parent_id=0 只取根级,正整数只取该文件夹的直接子级,省略则返回全部层级。

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

Input Schema

NameRequiredDescriptionDefault
scopeNo文档范围;省略=我可见的全部范围。
parent_idNo父文件夹 id:0=根级,正整数=该文件夹的直接子级,省略=全部层级。

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that the result is a bare array rather than a paginated wrapper, which is genuinely useful behavioral context, but the enumerated field list largely duplicates the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the folder-only constraint and the return shape before the filter semantics. The long field enumeration is the one part that does not earn its place, since the output schema already carries it.

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 two-parameter read-only listing tool with full schema coverage and an output schema, nothing an agent needs is missing: scope, hierarchy filtering, and return shape are all stated.

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 description's scope/parent_id explanations are essentially verbatim restatements of the schema descriptions. It adds no syntax, edge-case, or interaction detail beyond what the schema already provides, so the baseline 3 applies.

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 (list folders) and immediately scopes it with "只列文件夹(不含文档)", which separates it from the document-listing siblings. It also names the exact return shape, so an agent knows precisely what it gets back.

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?

Gives clear conditional semantics: omitting scope returns all visible folders, parent_id=0 returns only roots, a positive integer returns direct children, and omitting parent_id returns all levels. It does not explicitly name an alternative tool for listing documents, but the "不含文档" clause effectively routes that case away.

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