Skip to main content
Glama

ssuMCP

by org.duckdns.ssumcp
OverviewDiscussionsAdmin

get_my_schedule

Read-onlyIdempotent

SSU Campus(숭실대학교 캠퍼스)에서 인증된 학생의 u-SAINT 시간표를 과목별로 묶어 조회합니다. year와 term을 생략하면 현재 u-SAINT에서 선택된 학기를 반환하며, 특정 학기를 조회하려면 year와 term을 모두 전달하세요. term 값: 1=봄학기, 2=여름학기, 3=가을학기, 4=겨울학기. mcp_session_id 필요(SAINT 로그인). 미인증 시 loginUrl이 포함된 AUTH_REQUIRED를 반환하므로, loginUrl을 사용자에게 보여주고 브라우저에서 로그인하도록 안내한 뒤 발급된 mcp_session_id로 다시 호출하세요.

Input Schema

NameRequiredDescriptionDefault
termNo학기: 1=봄, 2=여름, 3=가을, 4=겨울. year와 함께 지정해야 함.
yearNo조회할 학년도(예: 2026). term과 함께 지정해야 함.
mcp_session_idNo선택 MCP session ID. 생략하면 현재 MCP transport에 안전하게 바인딩된 세션을 사용합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / mcp_session_id / description
      Previous value: -"start_auth(SAINT)로 발급받은 MCP session ID. 없거나 SAINT 미연동이면 loginUrl과 함께 AUTH_REQUIRED를 반환."New value: +"선택 MCP session ID. 생략하면 현재 MCP transport에 안전하게 바인딩된 세션을 사용합니다."
    • changedInput schema / required
      Previous value: -[
-  "mcp_session_id"
-]New value: +[]
  2. Changed3 schema fields changed
    • changedInput schema / properties / mcp_session_id / description
      Previous value: -"MCP session ID issued by start_auth(SAINT). If absent or SAINT not linked, returns AUTH_REQUIRED with a loginUrl."New value: +"start_auth(SAINT)로 발급받은 MCP session ID. 없거나 SAINT 미연동이면 loginUrl과 함께 AUTH_REQUIRED를 반환."
    • changedInput schema / properties / term / description
      Previous value: -"Academic term: 1=spring, 2=summer, 3=fall, 4=winter. Must be provided together with year."New value: +"학기: 1=봄, 2=여름, 3=가을, 4=겨울. year와 함께 지정해야 함."
    • changedInput schema / properties / year / description
      Previous value: -"Academic year, such as 2026. Must be provided together with term."New value: +"조회할 학년도(예: 2026). term과 함께 지정해야 함."
  3. Changed2 schema fields changed
    • addedInput schema / properties / term
      Added value: +{
+  "description": "Academic term: 1=spring, 2=summer, 3=fall, 4=winter. Must be provided together with year.",
+  "type": "integer"
+}
    • addedInput schema / properties / year
      Added value: +{
+  "description": "Academic year, such as 2026. Must be provided together with term.",
+  "type": "integer"
+}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses the authentication prerequisite, the AUTH_REQUIRED response with loginUrl, and the expected retry flow. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, all load-bearing: what it returns, default vs specific semester behavior, term codes, and auth retry instructions. No filler and the core purpose is front-loaded.

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 simple read tool with no output schema, this is complete: all parameters are covered, default behavior is specified, and the only notable edge condition (unauthenticated) is handled explicitly with a remediation path.

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 coverage is 100%, so the baseline is 3. The description adds meaning by explaining the term code mapping, the default current-semester behavior when year/term are absent, and the role of mcp_session_id in the login flow, which goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (u-SAINT timetable of an authenticated student at SSU Campus) and a specific action (retrieve grouped by subject). This is distinguishable from sibling tools like get_my_grades or get_lms_dashboard.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: omit year/term for the current u-SAINT semester, pass both for a specific one, and describes the auth failure flow. It does not explicitly name sibling alternatives or state when not to use it, so not a 5.

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

All ssuMCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources