Skip to main content
Glama

course_list

List PKU teaching-site courses with IDs, names, semesters, and hidden status; defaults to the current term and can include history or refresh data.

Instructions

教学网课程:course_id、名称、学期、hidden(用户标记的退课/不关注)。默认只列当前学期。

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

Input Schema

NameRequiredDescriptionDefault
refreshNo
include_historyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/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 burden. It usefully discloses default scope (current semester only) and the meaning of the 'hidden' flag, but says nothing about the effect of refresh, whether historical data is fetched, or read-only semantics. It adds real context but leaves behavior partially opaque.

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?

A single compact sentence with the resource front-loaded and the default scope stated last. Nothing is wasted, though the extreme terseness contributes to the parameter-coverage gap.

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

Completeness3/5

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

An output schema exists, so field returns need no elaboration, but for a two-parameter tool with no annotations and zero schema descriptions the description does too little parameter-level work. It is adequate to identify the tool but not to invoke it with confidence.

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%, so the description must explain both parameters, yet it never names 'refresh' or 'include_history'. The '默认只列当前学期' clause only loosely hints at include_history; refresh is entirely unexplained.

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 names the resource (教学网课程) and lists the fields it returns (course_id、名称、学期、hidden), making the operation recognizably a course listing. It does not explicitly contrast with siblings like course_hide or semester_sync, but the verb+resource is specific enough to distinguish it.

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 '默认只列当前学期' tells the agent the default scope, implying when to widen the query, and the parenthetical clarifies what 'hidden' means. However, there is no explicit when/when-not guidance versus alternatives, and no mention of when to set the two exposed parameters.

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