Skip to main content
Glama

assignment_list

List unsubmitted PKU teaching-site assignments sorted by deadline, showing due dates, submission status, grades, and attachments; filter by course, include hidden or submitted work, or refresh the cache.

Instructions

教学网作业:截止时间 due_at(没有钟点时只有 deadline_raw)、是否已交、最后提交时间、成绩、要求和附件,按截止排序。

默认只列未交、跳过 hidden 课程;缓存 10 分钟,refresh=true 强制重新抓取。
已交不等于已评分;只在公告里布置的任务不在这里,需要再看 announcement_list。

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": "assignment_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNo
course_idNo
include_hiddenNo
include_submittedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are supplied, yet the description carries the full burden well: it discloses a 10-minute cache with refresh=true forcing a refetch, the default filter set, the deadline sort order, and a real semantic gotcha (submitted is not the same as graded). It also warns about the deadline_raw fallback when no clock time exists, which 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight paragraphs: field/ordering scope first, then defaults, cache behavior, and the announcement caveat. Every sentence carries operational information and nothing is repeated from the schema or title.

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, the description need not explain return values, yet listing them still helps an agent select the tool. The only real gaps are the undocumented course_id parameter and no mention of authentication context for a 4-parameter tool with no annotations.

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 coverage is 0% and no annotations exist, so the description must compensate, and it explains refresh (forces refetch), include_submitted (default only unsubmitted), and include_hidden (hidden courses skipped by default). Only course_id is left unaddressed, though its meaning is largely self-evident from the name.

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?

Uses a specific verb+resource (lists teaching-site assignments) and enumerates the returned fields (due_at/deadline_raw, submission status, last submission time, grade, requirements, attachments) plus ordering by deadline. It explicitly distinguishes itself from announcement_list, telling the agent where announcement-only tasks live.

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?

States the default behavior clearly (only unsubmitted, hidden courses skipped) and gives an explicit exclusion with the alternative: tasks assigned only in announcements are not here, use announcement_list. No guidance is given for course_id scoping or how this relates to sibling tools like grade_list, so it stops short of a full when/when-not map.

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