WeDaka MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEDAKA_EMP_NO | Yes | Your employee number | |
| WEDAKA_API_URL | Yes | The URL of the WeDaka server | |
| WEDAKA_USERNAME | Yes | Your AD account username | |
| WEDAKA_DEVICE_ID | Yes | Your device UUID |
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 |
|---|---|
| wedaka_clock_inA | Clock in (上班打卡). Records the start of work for an employee. Supports custom date/time for retroactive entries. |
| wedaka_clock_outA | Clock out (下班打卡). Records the end of work for an employee. Supports custom date/time for retroactive entries. |
| wedaka_get_timelogA | Get employee time log records for a specific month. Returns clock-in/out times, leave records, and work day information. |
| wedaka_check_work_dayA | Check if a specific date is a work day. Returns the date type: 1=work day, 2=holiday, 3=weekend. |
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 4 tools
Each tool targets a distinct action (clock in, clock out, view logs, check work day) with no overlapping purposes. Descriptions clearly differentiate the functions.
All tools follow a consistent verb_noun pattern with the wedaka_ prefix, making the API predictable and easy to navigate.
4 tools is well-scoped for a time-tracking server, covering essential operations without unnecessary bloat or missing core actions.
The set covers the full clocking lifecycle: clock in, clock out, log retrieval, and work-day checking. While leave management appears in timelog data, it may be outside the server's intended scope.