Skip to main content
Glama

uplus_patrol

Patrols configured U+ courses, reports homework and experiment status in Markdown, collects outstanding answer briefs, and audits submitted objective answers for omissions or partial multi-selects.

Instructions

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. submit=True only submits homework that received valid answers; subjective, programming and file items are never auto-submitted.

audit is on by default: every already-submitted homework is re-checked for unanswered objective questions (漏答) and for multi-selects submitted with only part of the correct options (漏选). The platform only reveals its standard answer after grading and hides it while a submission is pending; a local journal of answers this tool submitted fills that gap. Multi-selects with neither source are reported as "unjudged", never silently as complete. The audit itself is read-only. Results also include repair_briefs: when a gap is found, answer the listed questions and call uplus_repair_homework to withdraw, complete and resubmit the homework. Set audit=False only to skip this extra read pass.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uplus_patrol"
  }
}

Input Schema

NameRequiredDescriptionDefault
auditNo
submitNo
auto_answerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.8
    • changedInput schema / properties / audit / default
      Previous value: -falseNew value: +true
  2. Changed1 schema field changedv0.7.5
    • addedInput schema / properties / audit
      Added value: +{
      +  "default": false,
      +  "title": "Audit",
      +  "type": "boolean"
      +}
  3. First observedv0.5.2

TDQS

A4.1/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it does substantial work: it discloses what is never auto-submitted (subjective, programming, file items), that the audit pass is read-only, that the platform hides standard answers while grading is pending, and that a local journal fills that gap. It omits operational traits such as runtime cost of patrolling every course and where the Markdown report is written, which matters for an agent deciding whether to call it.

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?

The core action and output are front-loaded in the first two lines, and the remaining paragraphs are organized by concern (submission rules, audit behavior, repair follow-up). It runs long with some restatement of the audit rationale, but almost every sentence adds a distinct behavioral fact.

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 complex, multi-course mutating tool with no annotations and no output schema, the description covers what the report contains, the safety boundary on submissions, the audit semantics, and the handoff to the repair sibling. The one real hole is the undefined auto_answer flag, which is the main thing an agent would be guessing about.

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%, so the description must define all three flags. It explains audit (default on, read-only, skip with False) and submit (restricted to validly answered homework) clearly, but auto_answer is never mentioned in the description and its schema entry is a bare boolean, leaving one parameter's behavior entirely undefined.

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 opening sentence states a specific verb and scope: patrol every configured course and write a Markdown report, then names exactly what the report contains (homework/experiments, submitted/pending/outstanding/takeover, answer briefs). This distinguishes it from the per-homework siblings like uplus_inspect_homework or uplus_audit_homework, which operate on individual items rather than the whole course set.

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 explicit conditions for its own flags (submit=True only submits homework with valid answers; audit=False only to skip the extra read pass) and routes the agent to uplus_repair_homework when repair_briefs appear. It does not say when to prefer this over uplus_list_homeworks or uplus_inspect_homework, so an agent still has to infer the relationship to read-only listing tools.

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