Skip to main content
Glama

uplus_answer_experiment

Fills an experiment report from section text, verifies required content and compliance checks, and submits it only after checks pass.

Instructions

Fill the experiment report, verify it, and submit it.

sections maps a section name (实验实现 / 实验结果 / 实验总结 …) to its text — the output of uplus_inspect_experiment's needed_sections. Server-derived sections from the handbook are merged in automatically; a supplied value overrides them.

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; force=True downgrades the checklist to warnings.

With submit=True (default) a passing report is uploaded and submitted, and the page is re-read until 「已提交」+「撤回」 appear — a mere upload is never reported as a successful submission. An already-submitted experiment is not re-submitted. submit=False stops after generating and verifying. student_name / student_id override the identity in the personal config.

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>",
      "sections": "<sections>"
    },
    "name": "uplus_answer_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
exp_idYes
submitNo
sectionsYes
course_idYes
stu_exp_idYes
student_idNo
student_nameNo
template_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.3

TDQS

A4.1/5.0
Behavior5/5

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

With zero annotations, the description carries the full disclosure burden and does so richly: it explains the inspection gate (non-empty body, no leftover placeholders, content match, cover fields, screenshots, handbook coverage, AI-sounding meta talk, repetition, layout), that a failed check submits nothing and returns reasons, and that force downgrades the checklist to warnings. It also discloses the verification loop that waits for 「已提交」+「撤回」 before claiming success, and the server-merge/precedence rule for handbook-derived sections. These are exactly the behaviors an agent cannot infer from the schema.

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?

It is front-loaded with the verb chain, then ordered logically: inputs, template origin, validation gate, submission semantics, identity overrides. Sentences are dense with information rather than padded. A few clauses (the full compliance checklist enumeration) are long but each item is actionable, so little is wasted.

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 9-parameter mutation tool with no annotations and no output schema, the description covers the essential flow, failure behavior, and success verification well. Remaining gaps are the meaning of the three identifier parameters and template_path, plus no statement of what a successful call returns to the caller beyond the submission state.

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 9 parameters, so the description must compensate and it only partially does: it defines sections (mapping section name to text, sourced from needed_sections, with supplied values overriding server-derived ones), force, submit, student_name, and student_id. course_id, exp_id, stu_exp_id, and template_path receive no explanation at all, which is a real gap for required identifiers the agent must supply correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line names three specific actions (fill, verify, submit) on a specific resource (the experiment report), which is far more than a tautology. It is distinguishable from siblings such as uplus_generate_experiment_report and uplus_submit_experiment_report because it explicitly bundles generation, gate-checking, and submission. It never names those siblings as alternatives, so the differentiation is implicit rather than stated.

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?

Clear context is given: this is the tool that turns uplus_inspect_experiment's needed_sections into a finished, submitted report, and submit=False is documented as the generate-and-verify-only mode. It also states the exclusion that an already-submitted experiment is not re-submitted. What is missing is an explicit statement of when an agent should prefer the separate generate/submit tools over this combined one.

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