Skip to main content
Glama
Sign In

ssuMCP

by org.duckdns.ssumcp
OverviewDiscussionsAdmin

get_room_available_seats

Read-onlyIdempotent

숭실대학교 도서관 특정 열람실의 모든 좌석 현황을 실시간으로 조회합니다. 좌석별 상태(available/occupied/away/inactive), 좌석 번호(label), 좌석 유형, 이석 시 잔여 시간(remainingTime, 분)을 반환합니다. roomId 가능한 값: 15(1열람실 B1F), 53(숭실스퀘어ON 2F), 54(오픈열람실 2F), 57(마루열람실 6F), 58(대학원열람실 6F), 59(리클라이너 5F), 60(숭실멀티라운지 5F). externalSeatId를 prepare_reserve_library_seat에서 사용하세요. compact=true이면 좌석 배열을 생략하고, offset/limit(최대 200)으로 페이지를 제한할 수 있습니다. mcp_session_id 필요(LIBRARY 로그인).

Input Schema

NameRequiredDescriptionDefault
limitNo최대 반환 좌석 수(1~200).
offsetNo좌석 상세 배열 시작 위치(0 이상).
roomIdYes열람실 ID. 가능한 값: 15(1열람실 B1F), 53(숭실스퀘어ON), 54(오픈열람실), 57(마루열람실), 58(대학원열람실), 59(리클라이너), 60(숭실멀티라운지).
compactNotrue이면 좌석 상세 배열을 생략합니다.
mcp_session_idNo선택 MCP session ID. 생략하면 현재 MCP transport에 안전하게 바인딩된 세션을 사용합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "true이면 좌석 상세 배열을 생략합니다.",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "최대 반환 좌석 수(1~200).",
+  "type": "integer"
+}
    • changedInput schema / properties / mcp_session_id / description
      Previous value: -"start_auth(LIBRARY)로 발급받은 MCP session ID."New value: +"선택 MCP session ID. 생략하면 현재 MCP transport에 안전하게 바인딩된 세션을 사용합니다."
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "좌석 상세 배열 시작 위치(0 이상).",
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[
-  "roomId",
-  "mcp_session_id"
-]New value: +[
+  "roomId"
+]
  2. Changed1 schema field changed
    • 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."
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint/destructiveHint annotations, the description discloses real-time behavior, possible seat statuses, the LIBRARY session/login requirement, pagination via compact/offset/limit, and the downstream use of externalSeatId. The only minor ambiguity is that 'mcp_session_id 필요' could be read as requiring the parameter, while the schema marks it optional; this is better interpreted as requiring a valid session.

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?

The description is front-loaded with purpose and return shape, then moves through room IDs, pagination, and authentication. Each sentence carries operational value, and the dense information is still scannable and well organized.

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?

Since there is no output schema, the description correctly supplies the key return fields and status values an agent needs to interpret results. Combined with full parameter documentation in the schema and safety-related annotations, the description is complete enough for an agent to invoke this tool correctly and understand what it returns.

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 description coverage is 100%, so the baseline is 3. The description adds floor-level context for roomId values (e.g., 15 = 1열람실 B1F), clarifies the 200-item limit, and explains how externalSeatId relates to reservation preparation. This goes beyond the schema without replacing it.

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 verb and resource: it performs a real-time query of all seat statuses for a specific library reading room and enumerates the returned fields (status, label, seat type, remainingTime). It also gives concrete roomId values, which distinguishes it from broader sibling tools like get_library_available_seats or get_library_seat_status.

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?

The description implies when to use the tool: when an agent needs per-seat status for a specific reading room, and it further explains that externalSeatId should be passed to prepare_reserve_library_seat. However, it does not explicitly contrast this tool with siblings such as get_library_seat_status or get_library_available_seats, nor state when not to use it.

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