Skip to main content
Glama

uplus_repair_homework

Withdraw a submitted homework, fill missing or partial answers, and resubmit it. Use after an audit flags gaps; submits only once every known gap has an answer.

Instructions

Withdraw a submitted homework, fill its gaps, and resubmit it.

Use after uplus_patrol (audit is on by default) reports a homework as missing (漏答) or partial (多选漏选). answers maps question_id (or question order as a string) to the corrected answer; the patrol result's repair_briefs lists exactly which questions need one. Answers already stored in the local journal (because this tool submitted the homework earlier) are used automatically, so a journal-covered partial can be repaired without new model answers.

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_answer_homework; subjective items never block the repair. verify_unjudged=True additionally re-answers multi-selects whose completeness could not be checked while the homework was pending grading.

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": {
      "task_id": "<task_id>",
      "course_id": "<course_id>"
    },
    "name": "uplus_repair_homework"
  }
}

Input Schema

NameRequiredDescriptionDefault
submitNo
answersNo
task_idYes
course_idYes
verify_unjudgedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.8

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the refusal precondition ('refuses to withdraw until every known gap has an answer'), the failure mode on graded homework ('reported without changing anything'), answer preservation and re-fill semantics, automatic journal reuse, and that subjective items never block submission. These are non-obvious invariants an agent could not 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?

Purpose is front-loaded in its own sentence, followed by preconditions, then parameter behavior, which is the right order for an agent. It is somewhat long and the 'existing answers are preserved and re-filled' point is restated in two clauses, but no sentence is filler.

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 multi-step mutation tool with no annotations, no output schema, and zero schema coverage, the description covers the risky behaviors: withdraw refusal, no-op on graded homework, journal fallback, and submission gating. Return-value shape is only hinted at ('reported without changing anything'), which is the main remaining gap.

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?

Schema description coverage is 0%, so the description must compensate. It explains the two non-obvious parameters well: `answers` maps question_id or question order as a string to a corrected answer, and `verify_unjudged` re-answers multi-selects whose completeness could not be checked while grading was pending. The `submit` flag's effect and the roles of `task_id`/`course_id` are left implicit, which keeps it short of a 5.

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 line states a concrete three-step verb sequence on a specific resource ('withdraw a submitted homework, fill its gaps, and resubmit'). It also distinguishes itself from uplus_patrol (upstream trigger) and uplus_answer_homework (same submission gate), so an agent can place it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the exact precondition ('Use after uplus_patrol ... reports a homework as missing (漏答) or partial (多选漏选)') and points to patrol's repair_briefs as the source of which questions need answers. It also states a hard exclusion: a graded homework cannot be withdrawn. Both when-to-use and when-not are explicit.

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