Skip to main content
Glama

grade_list

Query semester grades and GPA from the PKU campus portal, with optional term filtering, to review academic performance.

Instructions

各学期成绩与 GPA(校内门户)。term 形如 25-26-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": "grade_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNo
refreshNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it says nothing about the portal call being a network/auth-dependent fetch, whether results are cached, or what 'refresh' changes. The only real disclosure is that supplying term narrows the result set, which is useful but thin for a tool with zero annotation coverage.

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 short sentences with the resource and the key filter front-loaded; no filler. The term clause is telegraphic rather than fully structured, and the parenthetical source note could be folded in more cleanly, but nothing is wasted.

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 return values need not be explained, and the term semantics are covered. However, for a portal-backed fetch the description omits the refresh parameter's meaning and any dependency on prior authentication, which are material for calling it correctly.

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 coverage is 0%, so the description must compensate, and it partially does: it gives the term format ('25-26-1') and states its filtering effect, none of which the schema conveys. The second parameter, refresh, is never mentioned, leaving half the parameters undocumented anywhere.

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 ('各学期成绩与 GPA') and scope ('各学期'), plus the source ('校内门户'), so an agent can tell it retrieves semester grades rather than courses or assignments. It does not explicitly contrast itself with siblings like course_list or semester_sync, which keeps it from a 5.

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 only implied: the tool returns all semesters' grades unless term is supplied, which hints at a 'call with no args to get everything' pattern. There is no explicit statement of prerequisites (e.g. that auth_setup must have run) or of when to prefer this over other grade/course tools.

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