Skip to main content
Glama

paperbridge_download

Download selected XJTLU past exam paper PDFs from search results to your computer, archived by course code. Provide record IDs from search, up to 20; each PDF is downloaded and verified.

Instructions

将检索结果中选定的试卷 PDF 保存到本人电脑,按课程代码归档。record_ids 必须来自 paperbridge_search,一次最多 20 份,按顺序下载并校验 PDF;不返回 Cookie、token 或临时签名链接。

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": {
      "record_ids": "<record_ids>"
    },
    "name": "paperbridge_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
record_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: files are written locally (consistent with readOnlyHint=false), downloads happen in order, each PDF is verified, and the response deliberately excludes cookies, tokens, and signed URLs. The remaining gap is what a failed/partial verification looks like and whether re-downloads are skipped, but the disclosure is well above the annotation baseline.

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 is front-loaded in the first clause; every following clause (provenance, cap, ordering, verification, credential non-return) adds information. It is dense and bundles several concerns into one long sentence, but there is no filler.

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 single-parameter tool with no output schema, the description covers source of IDs, batch limit, ordering, verification, and output content restrictions — everything needed to invoke it correctly and interpret the result.

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?

Only one parameter with 0% schema description coverage, so the description carries the burden — it supplies the provenance constraint (must come from paperbridge_search) and restates the 20-item cap. It does not explain the numeric-string pattern, but the schema already enforces that.

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 concrete verb+resource: download selected exam-paper PDFs from search results and archive them locally by course code. The scope ('from search results', 'to your own computer') clearly separates it from paperbridge_search and paperbridge_details.

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?

Explicitly routes the agent: record_ids must originate from paperbridge_search, and at most 20 per call. It gives a clear precondition and a batch limit, though it does not state any when-not-to-use case (e.g. already-downloaded items) or name an alternative tool for bulk retrieval.

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