Skip to main content
Glama

GitPicker

create_release_link

获取 GitHub 仓库某个已发布版本(Release/Tag)的站内直连下载链接:源码 zip 或指定编译附件(exe/zip/deb 等资产)。tag 缺省自动取最新 Release。当用户要下载某个软件的发布版本/安装包(而非仓库源码)时使用,如“下载 obsidian 最新版”“下个 v2.3.1 的安装包”。链接由中国大陆服务器直连分发,无需访问 github.com。

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": "create_release_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoRelease/Tag 版本号(如 v146、v2.3.1),缺省自动用最新 Release
fileNo要下载的附件文件名(Release 里的资产,如 App_x64.zip);缺省下载源码 zip。不确定有哪些附件时先不带 file 调用,返回里会列出
repoYes仓库名,如 Mindustry
ownerYes仓库属主,如 asteroidsfall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it declares the two defaults (tag→latest Release, file→source zip), explains that omitting `file` returns an asset listing, and discloses the delivery mechanism (mainland-China direct distribution, no github.com access required). Remaining gaps are link lifetime/expiry and whether any auth is needed.

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?

Purpose and default behaviour are front-loaded, then use-case guidance, then delivery context — a sensible ordering. Four dense sentences with little waste, though the final sentence about mainland-China distribution could be trimmed if the link behaviour were covered elsewhere.

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 4-parameter, no-output-schema tool this is close to sufficient: purpose, defaults, discovery workflow, and distribution channel are all covered. It stops short of describing the returned link's lifetime or the failure modes for a bad tag/filename, which an agent would want for error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the field descriptions: it explains the consequence of omitting each optional parameter and prescribes a two-step discovery pattern (call bare, read the returned asset list, then re-call with `file`). That is genuine invocation guidance rather than restatement.

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 states a specific verb and resource: fetch an in-site direct download link for a published GitHub Release/Tag, either the source zip or a named compiled asset. It also draws the line against sibling behaviour (get_repo/list_releases are listings, not download-link generation) by scoping itself to '下载某个软件的发布版本/安装包(而非仓库源码)'.

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 gives a clear trigger condition ('when the user wants to download a release/installer rather than repo source') plus two concrete example utterances, and adds a real workflow rule: call without `file` first when the asset list is unknown. What it does not do is name an alternative tool (e.g. list_releases) for the exploratory case, so the routing guidance is strong but not exhaustive.

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