uplus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPLUS_CONFIG | No | Path to the personal course configuration file (config/courses.json). Example: config/courses.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| uplus_check_loginA | Check whether the attached browser session is signed into U+. |
| uplus_loginA | Sign in to U+ through the attached browser session. Ask the user which flow they prefer BEFORE calling:
Returns |
| uplus_list_coursesA | List every course attached to the signed-in account. |
| uplus_list_homeworksA | List homework status for one course, or all courses when omitted.
|
| uplus_list_experimentsA | List experiments and their submission state for one course. |
| uplus_read_experiment_detailB | Read experiment detail: requirements, material, deadline, submitted files. |
| uplus_generate_experiment_reportC | Generate a standard experiment report .docx file.
|
| uplus_submit_experiment_reportB | Upload and submit an experiment report file.
|
| uplus_download_experiment_materialsA | 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 Read-only against the platform. Use it after |
| uplus_inspect_experimentA | Read an experiment and return the authoring brief. Opens the experiment detail page, reads 实验提交物 / 实验手册 / 实验附件,
and (when The result separates:
|
| uplus_answer_experimentA | Fill the experiment report, verify it, and submit it.
The report is built from the downloaded 资料 template when one exists,
otherwise from the built-in format. Before anything is uploaded the
report must pass the inspection gate: non-empty body, no leftover
placeholders, content that matches this experiment, and the compliance
checklist (teacher-template cover fields, 实验名称 field, screenshots when
the handbook demands them, handbook requirement coverage, AI-sounding
meta talk, repetition, layout). A failed check returns the reasons and
submits nothing; With |
| uplus_audit_experimentA | Read-only completeness audit for a submitted experiment. Pulls the submitted report back when the page exposes a download link and checks it for an empty body, leftover placeholders and a report written for a different experiment. When the file cannot be downloaded, the audit says so and only checks the page record — it never reports an unchecked report as clean. It withdraws and submits nothing. |
| uplus_inspect_homeworkB | Return homework status plus a structured brief of its questions. The model reads the brief and returns an |
| uplus_answer_homeworkB | Fill objective questions and optionally submit.
|
| uplus_repair_homeworkA | Withdraw a submitted homework, fill its gaps, and resubmit it. Use after The tool refuses to withdraw until every known gap has an answer. A graded
homework cannot be withdrawn and is reported without changing anything.
Existing answers are preserved and re-filled, so a withdrawal that clears
the draft still leaves enough answers to resubmit. Submission uses the same
gate as |
| uplus_capture_question_imageA | Screenshot one question block and return it as an image. Use for figure questions — a stem whose diagram/picture carries the part
that makes the statement true or false (for example "以下模型是…" with a
crypto diagram). The question text alone cannot be answered reliably, and
the model cannot see an The tool opens the answer page, navigates to the question by its stem
(same rule as filling), and captures that question's container — not just
the viewport — so the whole figure is readable. It fills and submits
nothing. Identify the question with
|
| uplus_audit_homeworkA | Read-only completeness audit for one homework (no withdraw, no submit). Every question is read from the student-side detail, so an already
submitted homework can be audited safely. A question counts as answered
only when its The API status understates (a handed-in homework may read as not submitted),
so |
| uplus_upload_attachmentC | Attach a local file (PPT/PDF/ZIP) to a homework that requires an upload. |
| uplus_patrolA | Patrol every configured course and write a Markdown report. Lists homework and experiments, separates submitted / pending / outstanding /
takeover items, and collects answer briefs for outstanding objective
questions.
|
| uplus_closeA | Detach from the browser and release the worker session. |
| browse_launch_edgeA | Launch an installed browser (Edge / Chrome) with a CDP debug port on a dedicated profile copy, then verify the port listens. The tool name keeps the original |
| browse_openB | Open a URL in the attached browser tab and return its title/status. |
| browse_snapshotC | Return a compact snapshot: interactive elements (selector/role/text) + visible text. |
| browse_clickC | Click an element by CSS selector or by visible text. |
| browse_fillC | Replace an input's value, optionally pressing Enter afterwards. |
| browse_typeC | Type text with a human-like delay into a focused/selected element. |
| browse_pressB | Press a key or combination, e.g. |
| browse_scrollA | Scroll the page by pixels, or scroll a specific element into view. |
| browse_get_textA | Read the text content of an element (defaults to the whole body). |
| browse_eval_jsC | Evaluate a JavaScript expression in the page and return its JSON value. |
| browse_screenshotB | Screenshot the page: returns a path, or base64 when no path is given. |
| browse_wait_forC | Wait until a selector exists or text appears. |
| browse_tabsA | List open tabs with url/title and which one is active. |
| browse_switch_tabB | Switch the active tab by index from |
| browse_backB | Navigate back one history entry. |
| browse_uploadC | Set files on an |
| browse_select_optionC | Choose an option in a |
| browse_act_batchA | Run one short batch of page actions; stop on failure or navigation. Each step supports: Returns completed steps, remaining count, extract rows and a failure or
navigation receipt. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 38 tools
Most U+ domain tools have distinct intents, but several experiment tools overlap heavily: uplus_read_experiment_detail, uplus_inspect_experiment, uplus_download_experiment_materials, and uplus_audit_experiment all read related experiment data. Similarly, uplus_generate_experiment_report, uplus_answer_experiment, and uplus_submit_experiment_report can be confused, and uplus_inspect_homework/audit_homework/answer_homework/repair_homework form a dense cluster. The detailed descriptions mitigate this, but boundaries are not always obvious at a glance.
Tool names use two clear, consistent namespaces: uplus_* for domain operations and browse_* for browser primitives, all in snake_case with predictable verb_noun forms. Minor deviations exist, such as the legacy browse_launch_edge spelling and uplus_close as a bare verb, but overall the pattern is easy to follow.
At 38 tools, the surface is heavy: 20 domain-specific U+ operations plus 18 generic browser primitives. While some browser tools are useful fallbacks, the generic low-level operations (click, fill, type, press, scroll, eval, snapshot, batch) add substantial weight beyond the core course/homework/experiment workflow.
The domain surface covers a full lifecycle: login, course listing, homework inspection/answering/auditing/repairing/submitting, experiment inspection/material download/report generation/answering/submission/auditing, plus attachment upload and image capture. Browser primitives provide fallback navigation and interaction. Minor gaps remain, such as a dedicated browser navigation tool outside batch/open, but agents can work around them.