seoultech_c4t
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_loginA | 로그인 세션이 없거나 만료됐을 때 사용자가 직접 로그인할 Chrome 창을 연다. |
| list_coursesA | 현재 수강 중인 과목 목록을 조회한다. |
| list_noticesC | 전체 과목 또는 지정한 과목의 공지 목록, 게시일과 전체 본문을 조회한다. |
| search_noticesA | 공지 전체 본문에서 검색하고 각 결과의 게시일도 함께 반환한다. |
| list_assignmentsB | 전체 과목 또는 지정한 과목의 과제, 마감일, 제출 여부를 조회한다. |
| get_pending_assignmentsC | 현재 미제출이거나 제출 여부가 확인되지 않은 과제를 마감일 순으로 조회한다. |
| get_upcoming_deadlinesB | 오늘부터 지정한 일수 안에 마감되는 미제출 과제를 조회한다. |
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 7 tools
Most tools target clearly distinct resources: courses, notices, assignments, and login. However, get_pending_assignments and get_upcoming_deadlines overlap significantly—both return pending assignments sorted by due date, with the only real difference being the time-window filter. list_notices and search_notices are also similar but the search functionality makes their purposes distinguishable.
All tools follow a consistent verb_noun snake_case pattern: list_*, search_*, get_*, and start_login. The verbs clearly indicate the action and the nouns match the resource being acted on. No mixed conventions or vague names.
Seven tools is a well-scoped size for a university course-management integration. Each tool covers a meaningful user need without redundancy, and the count falls comfortably within the ideal 3-15 range.
The tool set covers the core read-only workflows: login handling, course listing, notice browsing/searching, and assignment retrieval with deadline awareness. Minor gaps exist, such as no way to view individual course/assignment details or access attachments, but agents can complete typical student tasks without dead ends.