weekly-records
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weekly_recordsA | week-one 또는 week-two의 가상 팀 업무 기록을 읽습니다. 반환값은 주차, 팀 이름, 기간 시작일, 보고 기준일, 업무 기록 목록입니다. 파일을 수정하지 않으며 완료·진행·위험 판정이나 보고서 작성은 하지 않습니다. |
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 1 tool
With only one tool, there is no possibility of confusion or misselection. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (get_weekly_records) and is descriptive. Consistency is not an issue with only one tool.
A single tool is too few for a server, even if the scope is narrow. The rubric explicitly marks one tool as too few, and this feels thin for a dedicated 'weekly-records' server.
The tool fully covers the read operation for weekly records, including both week-one and week-two. However, it only retrieves data and does not offer any related operations (e.g., listing weeks, summarizing), though the stated purpose is read-only.