Skip to main content
Glama

ssuMCP

by org.duckdns.ssumcp
OverviewDiscussionsAdmin

wait_for_library_seat

숭실대학교 중앙도서관 좌석에 대한 백그라운드 대기 intent를 등록합니다. 이 호출 자체가 사용자의 동의이며, 등록 후 조건에 맞는 좌석이 나오면 서버 워커가 이후 confirm_action 호출 없이 자동으로 예약할 수 있습니다. mcp_session_id 필요(LIBRARY 로그인).

Input Schema

NameRequiredDescriptionDefault
floorNo선호 층: 2, 5, 6, 2F, 5F, 6F 중 하나.
room_idsNo선호 Pyxis room ID. JSON 배열 또는 CSV 형식, 예: [57,58] 또는 57,58.
mcp_session_idNo선택 MCP session ID. 생략하면 현재 MCP transport에 안전하게 바인딩된 세션을 사용합니다.
target_seat_idNo가용 시 예약할 고정 Pyxis 좌석 ID.
seat_attributesNo필수 속성. JSON 객체/배열 또는 CSV 형식: window,outlet,standing,edge,quiet,nearEntrance.
expires_in_minutesNo대기 만료 시간(분). 기본 120분.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / mcp_session_id / description
      Previous value: -"start_auth(LIBRARY)로 발급받은 MCP session ID."New value: +"선택 MCP session ID. 생략하면 현재 MCP transport에 안전하게 바인딩된 세션을 사용합니다."
    • changedInput schema / required
      Previous value: -[
-  "mcp_session_id"
-]New value: +[]
  2. Changed6 schema fields changed
    • changedInput schema / properties / expires_in_minutes / description
      Previous value: -"Wait expiry in minutes. Defaults to 120 minutes."New value: +"대기 만료 시간(분). 기본 120분."
    • changedInput schema / properties / floor / description
      Previous value: -"Preferred floor: 2, 5, 6, 2F, 5F, or 6F."New value: +"선호 층: 2, 5, 6, 2F, 5F, 6F 중 하나."
    • changedInput schema / properties / mcp_session_id / description
      Previous value: -"MCP session ID issued by start_auth(LIBRARY)."New value: +"start_auth(LIBRARY)로 발급받은 MCP session ID."
    • changedInput schema / properties / room_ids / description
      Previous value: -"Preferred Pyxis room IDs as JSON array or CSV, e.g. [57,58] or 57,58."New value: +"선호 Pyxis room ID. JSON 배열 또는 CSV 형식, 예: [57,58] 또는 57,58."
    • changedInput schema / properties / seat_attributes / description
      Previous value: -"Required attributes as JSON object/array or CSV: window,outlet,standing,edge,quiet,nearEntrance."New value: +"필수 속성. JSON 객체/배열 또는 CSV 형식: window,outlet,standing,edge,quiet,nearEntrance."
    • changedInput schema / properties / target_seat_id / description
      Previous value: -"Fixed Pyxis seat ID to reserve when available."New value: +"가용 시 예약할 고정 Pyxis 좌석 ID."
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the most important behavioral trait: this call is user consent, and a server worker may automatically reserve a matching seat without any subsequent confirm_action. It also makes the background nature and session/login requirement explicit, which annotations alone do not convey.

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?

Two dense sentences front-load the core purpose and then add the critical consent and auto-reservation caveat. There is no filler, repetition of schema fields, or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a background-registration tool with no output schema, the description sufficiently covers invocation semantics: what it does, what side effects occur, and the session requirement. It does not describe the return value or how to check/cancel the wait, but the core calling context is complete given the rich schema and annotations.

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 100%, so the baseline is 3. The description adds only that mcp_session_id requires a LIBRARY login, which is useful context but slightly conflicts with the schema marking that parameter as optional. No additional meaning is added for the other five parameters.

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 states a specific action: registering a background wait intent for library seats, and clearly distinguishes itself from sibling tools by noting that it leads to automatic reservation without a confirm_action call. This is a concrete verb+resource combination that separates it from prepare_reserve_library_seat and reservation flow tools.

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 context on when to use this tool: when the user wants to wait for a matching seat and consents to automatic reservation without further confirmation. It also states the prerequisite of a LIBRARY login session. It does not explicitly list alternative tools or exclusion cases, but the contrast with confirm_action provides strong implicit guidance.

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