Skip to main content
Glama

GitPicker

list_files

列出 GitHub 仓库的全部文件路径(带大小)。当需要了解仓库结构、寻找特定文件时使用。branch 缺省时自动使用默认分支。支持 path_prefix 前缀过滤与 glob 模式过滤(如 .md、src/**/.ts),文件很多时建议缩小范围。

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
globNoglob 模式过滤文件路径:* 单段任意、** 跨目录、? 单字符,如 *.md、src/**/*.ts
repoYes仓库名
ownerYes仓库属主
branchNo分支名,缺省用默认分支
path_prefixNo路径前缀过滤,如 src/lib/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses useful behavior: results include file sizes, the default branch is used when branch is omitted, and large repos should be narrowed. It says nothing about authentication requirements, rate limits, or whether results are truncated or paginated for very large repositories — the main risk when listing every path.

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?

The purpose is front-loaded in the first clause, followed by when-to-use guidance and then filtering details. Every sentence carries information; no filler. It is slightly dense but appropriately sized for a five-parameter tool.

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 read-only listing tool with no output schema and no annotations, the description covers what is returned (paths plus sizes), how branch defaults work, and how to filter. The remaining gap is response-size behavior on huge repos, which it warns about but does not bound.

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%, so the baseline is 3, and the schema already documents branch fallback, glob syntax, and path_prefix examples. The description repeats the glob examples and default-branch behavior rather than adding new meaning, such as how path_prefix and glob interact when combined.

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 gives a concrete verb and resource: '列出 GitHub 仓库的全部文件路径(带大小)'. It also implicitly separates this tool from read_file by saying to use it to understand repo structure or locate a file. It never names a sibling tool, so the differentiation is left implicit rather than explicit.

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?

It states a clear trigger ('当需要了解仓库结构、寻找特定文件时使用') and operational advice ('文件很多时建议缩小范围'). It does not name alternatives such as read_file for fetching content, or state when not to use this tool, so the routing guidance stops just short of the top score.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources