Skip to main content
Glama

announcement_list

Retrieve course announcements from PKU's teaching site with titles, publish times, authors, content, and attachments; filter by course or include historical posts as needed.

Instructions

教学网公告(新到旧):标题、发布时间、发布人、正文、附件。默认汇总本学期未隐藏的课程。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
refreshNo
course_idNo
include_historyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses ordering (newest to oldest) and the default scoping (current semester, hidden courses excluded), which is genuine behavioral value. It says nothing about caching/refresh semantics, pagination/limit behavior, or how include_history changes results.

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, front-loaded with the resource and ordering, then the default scope. No filler, though the field enumeration is somewhat redundant given an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with zero schema description coverage and no annotations, the description leaves key knobs (limit, refresh, include_history) undocumented. The presence of an output schema excuses it from explaining return values, but the input-side gaps remain significant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters, so the description must compensate and does not. The default scope sentence loosely implies course_id and include_history semantics, but limit and refresh (likely a cache-refresh flag) are entirely unexplained in both schema and description.

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+resource (announcement listing) plus the ordering (newest to oldest) and the returned fields (title, publish time, publisher, body, attachments). It clearly reads as distinct from sibling list tools such as assignment_list or grade_list, though it does not name any sibling explicitly.

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?

The sentence '默认汇总本学期未隐藏的课程' establishes the default scope, which implies when the tool is useful (current-semester announcements). However it gives no when-not-to-use guidance, no mention of alternatives for other semesters or courses, and no prerequisites for using the parameters to widen scope.

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