Skip to main content
Glama

kupid_room_schedule

Query the integrated undergraduate and graduate class schedule for any building or room at Korea University to determine occupancy. Filter by day, semester, and campus.

Instructions

건물/강의실의 정규 수업 시간표를 조회합니다 (학부+대학원 통합, SSO 로그인 필요).

"이 강의실 오늘 비어있나?" 확인용. 학부 22개 + 대학원 38개 단과대를 병렬 호출하므로 호출당 30~60초 소요 (총 800+ 학과 fan-out). 같은 학기는 자주 안 바뀌니 결과를 호출 측에서 캐싱 권장.

한계:

  • 학사 시스템에 등록된 정규 수업만 잡힘

  • 학회·세미나·임시 행사 등 비정규 점유는 별도 (spacek.korea.ac.kr 시스템 영역)

Args: building: 건물명 부분일치 (예: "애기능" → "애기능생활관" 매치) room: 호실 부분일치 (예: "301" → "301호" / "B301"). 비우면 건물 전체. day: 요일 필터 ("월"/"화"/.../"토"/"일"). 비우면 전 요일. year: 학년도 (기본값: 현재 학기 기준 자동) semester: 학기 ("1","2","summer","winter") campus: "1"=서울, "2"=세종 include_grad: True(기본)면 대학원도 검색, False면 학부만

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buildingYes
roomNo
dayNo
yearNo
semesterNo
campusNo1
include_gradNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, description effectively discloses behavioral traits: requires SSO login, takes 30-60 seconds due to parallel calls, and recommends caching. Limitations about only covering regular classes are also stated.

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?

Well-structured with front-loaded purpose and organized sections (usage context, limitations, parameters). Slight verbosity in parameter list could be trimmed, but overall efficient.

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?

Description covers input parameters, usage context, performance characteristics, limitations, and caching advice. Output schema exists, so return values need not be explained. Complete for a complex query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has no descriptions (0% coverage), but the description's Args block adds detailed semantics for each parameter, including partial matching, defaults, and examples, fully compensating.

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?

Description clearly states it queries regular class schedules for buildings/rooms, integrated for undergrad and graduate. While sibling tools exist, none are directly comparable for room schedules, so no explicit differentiation is needed.

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?

Provides context for checking room availability and mentions performance and caching, but does not explicitly state when not to use or list alternative tools for non-regular schedules.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SonAIengine/ku-portal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server