se-notion
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKLOG_DB_ID | Yes | Notion database ID for work logs | |
| NOTION_API_KEY | Yes | Notion Integration Token issued from Notion Developers | |
| MAINTENANCE_DB_ID | Yes | Notion database ID for maintenance sites | |
| TROUBLESHOOTING_DB_ID | Yes | Notion database ID for troubleshooting records |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_maintenance_siteB | 유지보수 사이트(고객사) 정보를 등록하거나 기존 사이트 정보를 갱신합니다. 기존 동일 사이트가 있을 경우 덮어쓰지 않고 기존 페이지를 스마트 업데이트합니다. |
| add_work_logB | 업무 일지 및 정기점검 수행 기록을 노션 업무일지 DB에 등록합니다. |
| add_troubleshootingC | 에러 및 트러블슈팅 조치 내역을 노션에 적재합니다. |
| list_maintenance_sitesB | 등록된 유지보수 사이트 목록을 조회합니다. |
| list_work_logsC | 업무 일지 목록을 조회합니다. |
| search_troubleshootingC | 트러블슈팅 해결 사례를 검색합니다. |
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 6 tools
Each tool targets a distinct resource (maintenance sites, work logs, troubleshooting) with a clear action (add/list/search), so selection is generally unambiguous. Minor overlap exists between add_work_log and add_troubleshooting since a troubleshooting record could be seen as a work log, but the descriptions differentiate them adequately.
All six tools follow a clean verb_noun pattern (add_, list_, search_ + resource), with no mixed conventions or vague verbs. The pattern is entirely predictable and readable.
Six tools is well-scoped for a Notion-based maintenance tracking server covering three resource types. The set is slightly thin in that each resource gets only one or two operations, but every tool earns its place.
The surface covers create/list for sites and work logs and add/search for troubleshooting, plus site upsert. However, update and delete operations are absent for work logs and troubleshooting, and there is no single-item retrieval, leaving notable lifecycle gaps.