Skip to main content
Glama

uplus_download_experiment_materials

Downloads an experiment's attachments, manual file links, and matching course files, then reports the template to use for report authoring.

Instructions

Download an experiment's materials from all sources.

Downloads every attachment from the 实验附件 tab, every file link from the 实验手册 tab, and every matching file from the course 资料 section (recursing into folders). The best template across all sources is identified and reported in template / template_source.

Read-only against the platform. Use it after uplus_list_experiments (which returns exp_id / stu_exp_id) when you want the requirement files and the template on disk before authoring the report. Files go to reports/experiment_materials/.

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": {
      "course_id": "<course_id>",
      "exp_id": "<exp_id>",
      "stu_exp_id": "<stu_exp_id>"
    },
    "name": "uplus_download_experiment_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
exp_idYes
course_idYes
stu_exp_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.3

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: read-only against the platform, recursion into folders, best-template selection surfaced via template/template_source, and a concrete destination path reports/experiment_materials/. It omits overwrite behavior, authentication expectations, and what happens on partial failures, so not a 5.

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?

Front-loaded with the action and scope, then source enumeration, then preconditions and destination, which is a sensible reading order with little waste. The bold emphasis and multi-line layout are mildly noisy but not padding.

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 three-parameter download tool with no output schema, the description covers sources, template reporting, destination directory, and workflow placement well enough to invoke correctly. It stops short of describing the return payload shape or error handling, which matters for an agent expecting files on disk.

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 0% across three required parameters, and the description only partially compensates: it explains where exp_id and stu_exp_id come from (uplus_list_experiments) but says nothing about course_id or the format/relationship between exp_id and stu_exp_id. The partial coverage justifies a middle score rather than a low one.

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 first sentence supplies a specific verb (Download) and resource (experiment materials) plus the key scope word 'all sources', then enumerates the three sources: 实验附件 attachments, 实验手册 file links, and course 资料 files with folder recursion. This is clearly distinguishable from uplus_list_experiments and the read/answer/audit siblings.

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 an explicit prerequisite and ordering: use it after uplus_list_experiments (which yields exp_id/stu_exp_id) when you want requirement files and the template on disk before authoring the report. There is no explicit when-not-to-use or comparison against other material-reading siblings such as uplus_read_experiment_detail, which keeps it at 4.

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