Skip to main content
Glama

schedule_list

Retrieve your personal PKU course timetable, including class times, locations, teachers, week ranges, odd/even weeks, and exam arrangements by weekday, date, or term.

Instructions

个人课表(校内门户):星期、节次与钟点、地点、教师、周次、单双周、考试安排。

weekday 取 mon…sun;date 取 YYYY-MM-DD 会换算成星期。term 形如 26-27-1,默认当前学期。 工具不推断教学周,单双周需要结合当前是第几周判断。

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

Input Schema

NameRequiredDescriptionDefault
dateNo
termNo
refreshNo
weekdayNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full load and does disclose real behavioral traits: it reads from the campus portal, term defaults to the current semester, a date input is silently converted to a weekday, and — most usefully — the tool does not infer teaching weeks, so odd/even week must be resolved against the current week number. That last point is a genuine limitation an agent would otherwise get wrong. It stops short of covering the refresh parameter's effect or what happens when the portal session is not authenticated.

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 layout is sensible: returned fields first, then per-parameter formats, then the week-inference caveat. Nearly every clause carries information the schema does not. The dense field enumeration in the opening line is slightly list-like, but it earns its place as a capability summary.

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

Completeness5/5

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

For a four-parameter read tool with an output schema (so return shape needn't be restated), the description covers purpose, input formats, defaults, and the one non-obvious semantic trap around teaching weeks. The only minor omission, refresh behavior, is a small gap against an otherwise complete picture.

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 description coverage is 0%, so the description must compensate, and it largely does: weekday's accepted values (mon…sun), date's format (YYYY-MM-DD) plus its conversion behavior, and term's shape (26-27-1) with its default are all spelled out. Only refresh (boolean, default false) is left completely unexplained, which keeps this below a 5.

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 a specific resource (个人课表 from 校内门户) and enumerates exactly what it returns: weekday, period and clock time, location, teacher, week numbers, odd/even weeks, and exam arrangements. That is far more concrete than a restatement of the name. It does not, however, contrast itself with the sibling course_list, which an agent could plausibly confuse with a timetable tool.

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?

Usage is implied rather than stated: the agent can infer this is the tool for 'show me my timetable', and the term/date/weekday notes hint at filtering scenarios. But there is no explicit when-to-use or when-not-to-use guidance and no reference to an alternative, so the agent must infer the boundary with course_list on its own.

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