Skip to main content
Glama

GitPicker

get_download_progress

查询打包下载的实时进度。create_bundle_link 返回的是一次性下载链接,大仓库打包需要几分钟——用户等待或下载未完成时,把原链接传入本工具查询进度(拉取了几个仓库、压缩回传了多少 MB、有哪些被跳过)。压缩回传阶段返回已回传 MB 数,多次轮询可判断是否仍在推进。

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": {
      "url": "<url>"
    },
    "name": "get_download_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYescreate_bundle_link 返回的下载链接(原样传入)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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, and it does most of the work: it sets latency expectations (packaging a large repo takes minutes), describes what progress fields are reported (repos fetched, MB compressed/returned, skipped items), and explains that repeated polling reveals whether progress is still advancing. Gaps remain around the one-time link’s expiry behaviour and what is returned on error.

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, followed by the source of the URL, usage timing, and return semantics, all in two dense sentences. It is slightly packed, but no sentence is filler, and every clause adds operational information.

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?

With no annotations and no output schema, the description still tells the agent what will be returned and how polling interprets the result, which is enough for a single-parameter progress poll. More complete coverage of expiry and error states would raise this score, but nothing critical for a correct call is missing.

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?

There is a single parameter, and schema coverage is 100%, so the schema already documents it fully, including the instruction to pass the link as-is. The description adds useful context that the link is one-time and comes from create_bundle_link, but that mostly repeats the schema and does not add syntax or format detail beyond it. This makes a baseline of 3 appropriate.

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 begins with a specific verb+resource: querying real-time progress of a packaged download. It explicitly distinguishes itself from create_bundle_link, which produces the link, while this tool consumes it. An agent can tell the two apart without opening either 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 the trigger condition clearly: when the user is waiting or the download has not finished, pass the original link from create_bundle_link into this tool. It also explains polling as legitimate usage. It does not state when NOT to use it (for example, after the link is used or expired), so it falls short of a full when/when-not/alternatives treatment.

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