dorms-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_my_appsA | 도름스(dorms.school)에 내가 올린 앱(공동 게시 포함) 목록을 가져온다. 각 앱의 id(post_app_update, get_app_feedback 에 쓰는 UUID), 이름, 받은 도름 수, 댓글 수, 마지막 업데이트 시각을 준다. |
| post_app_updateA | 도름스에 올린 내 앱에 업데이트 노트를 게시한다. 그 앱에 도름을 준 선생님들에게 알림이 가고, 앱 카드에 '업데이트' 배지가 붙는다. app_id 는 list_my_apps 로 확인한 UUID. body 는 무엇이 새로워졌는지(1~4000자, 한국어 권장). version 은 선택(예: '1.2'). |
| get_app_feedbackA | 내 앱에 달린 최근 댓글 20개와 받은 도름 수를 가져온다. 어떤 점이 좋았는지, 어떤 개선 요청이 있는지 파악해 다음 업데이트에 반영할 때 쓴다. app_id 는 list_my_apps 로 확인한 UUID. |
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 3 tools
Each tool has a distinct job: list_my_apps discovers apps and UUIDs, get_app_feedback retrieves detailed comments for one app, and post_app_update is the only write action. Though list_my_apps and get_app_feedback both report counts, their purposes are clearly separated by summary versus detail.
All tool names follow the same lowercase snake_case verb_noun pattern: list_my_apps, get_app_feedback, post_app_update. The verbs are consistent and the resource nouns map directly to what each tool does.
Three tools is well-scoped for a server whose purpose is the app feedback/update loop. Each tool earns its place and there is no redundant tool padding the surface.
The core workflow is covered end to end: list apps, retrieve feedback, publish an update. Minor gaps exist such as no pagination for older comments or no way to reply to feedback, but they do not break the main use case.