HDU Academic System MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hdu_loginC | 登录杭电教务处系统 |
| get_course_scheduleB | 获取课程表（需要先登录） |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one handles authentication (hdu_login) and the other retrieves data (get_course_schedule). There is no overlap in functionality, and the dependency relationship (login required for schedule) is logically clear, preventing misselection.
The tool names follow a consistent verb_noun pattern (hdu_login and get_course_schedule), with both using snake_case. The slight deviation is that 'hdu_login' includes a domain prefix, but this is minor and does not break readability or predictability.
With only 2 tools, this server feels under-scoped for an academic system. While login and schedule retrieval are core functions, typical academic systems would include more operations (e.g., get_grades, register_courses, view_notices), making this set too thin for the apparent domain.
The tool surface is severely incomplete for an academic system. It covers authentication and one data retrieval function, but lacks essential operations like viewing grades, managing registrations, or accessing announcements. This will likely cause agent failures when trying to perform common academic tasks.