Skip to main content
Glama

GitPicker

list_releases

列出 GitHub 仓库的 Release 版本(版本号、名称、发布说明摘要、附件数)或 Git tag。当用户想知道某软件有哪些版本、看某个版本的更新内容时使用;要下载某个版本用 create_release_link。

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

Input Schema

NameRequiredDescriptionDefault
repoYes仓库名
ownerYes仓库属主

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully notes that results include version number, name, release-notes summary, and asset count, which tells the agent what to expect back. However, it says nothing about ordering, pagination, authentication requirements, rate limits, or whether prerelease/draft versions are included.

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 returned-field list is front-loaded in the first clause and the usage rule follows immediately, with zero filler. It is a single dense Chinese sentence chain, but every clause carries information.

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?

For a two-parameter read tool with no output schema, the description is mostly sufficient and its field enumeration substitutes for a return spec. The unresolved release-vs-tag duality and the absence of any ordering or pagination note leave an agent without enough to predict results reliably.

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 coverage is 100%, so owner and repo are already documented and the description adds no parameter detail. The notable omission is that the releases-vs-tags choice has no corresponding parameter, and the description does not explain how that selection is made. Baseline 3 applies when the schema does the parameter work.

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?

The description names a specific verb and resource ('列出 GitHub 仓库的 Release 版本...或 Git tag') and enumerates the returned fields (版本号、名称、发布说明摘要、附件数). It also distinguishes itself from the adjacent download tool by name. An agent can tell it apart from siblings 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 Guidelines4/5

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

It states concrete usage: when the user wants to see which versions exist or wants to inspect a version's changelog, and explicitly tells the agent to use create_release_link for downloading. That is a clear when-to-use plus one named alternative. The gap is that it never says how to choose between listing Releases and listing Git tags, leaving a routing decision unexplained.

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