USTC BB MCP

Overview Schema Source Related Servers Discussions Admin

bb_list_assignments

Read-onlyIdempotent

Lists course assignments and tests with deadlines and submission status, or scans all courses to identify what is due and what remains unsubmitted.

Instructions

列出作业和测试入口、DDL及提交状态；course='all' 扫描全部课程。unknown不能算已提交。

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": "<course>"
    },
    "name": "bb_list_assignments"
  }
}

Input Schema

Name	Required	Description	Default
`course`	Yes

Output Schema

Name	Required	Description	Default
`ok`	No
`data`	No
`error`	No
`message`	Yes
`complete`	No
`warnings`	No
`checked_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already declare this tool as read-only, idempotent and open-world, so the safety profile is covered. The description adds two useful behavioral facts: 'all' broadens the scan across all courses, and an 'unknown' status must not be treated as submitted. It says nothing about cost, volume or pagination when scanning every course, which is the main behavioral risk here.

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?

Two compact clauses with the scope rule and the data caveat front-loaded and no filler. The final clause 'unknown cannot count as submitted' is terse to the point of being slightly cryptic about what 'unknown' refers to.

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?

With an output schema present, return fields need not be described, and for a one-parameter read tool the description covers scope, a sentinel value and a result-interpretation caveat. The only meaningful gap is how to specify a single course, plus any note on volume when scanning all courses.

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 carries the burden for the single 'course' parameter. It explains the special sentinel value 'all' well, but never says what a normal value looks like (course ID, name, or code), leaving the common case undocumented.

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 description states a specific verb and resource (list assignment and test entries) and even names the fields returned: deadlines and submission status. That is enough to separate it from bb_assignment_details and bb_submit_assignment, but it never explicitly contrasts itself with those siblings.

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

Usage Guidelines3/5

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

It gives one concrete usage rule, namely that course='all' scans every course, which is a real branching instruction. It does not say when to prefer this over bb_assignment_details, nor does it state any prerequisites such as being logged in via bb_login.

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

Deploy Server