attendance-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATTENDANCE_DB | No | Optional path to a SQLite database file. If set to a non-existent path, the database is created and seeded. If set to an existing file, it is opened read-only and never seeded. If not set, an in-memory database is used. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_locationsA | List every site with its country, timezone and headcount. Also returns the date range the data covers. |
| find_late_arrivalsA | List individual late clock-ins, worst first. Use for 'who was late on X' questions. |
| repeat_late_arrivalsA | Rank employees who were late repeatedly, with late count, late rate and average minutes late. Use for 'who is regularly late' questions. |
| employee_attendanceA | Attendance summary and incident list (late, no-show, missed clock-out) for one employee. Accepts an employee ID or part of a name; if several people match, returns up to 20 candidates instead. |
| location_trendsA | Late rate and no-shows per site, grouped by weekday or by week. Use to spot site-level patterns such as a bad day of the week. Weekly rows carry partial_week=true when the date range cuts into that week. |
| missing_clock_eventsA | List no-shows (scheduled shift, no clock-in) and missed clock-outs (clocked in, never clocked out). |
| repeat_missing_clock_eventsA | Rank employees by no-shows and missed clock-outs, with counts and rates. Use for 'who keeps not turning up' or 'who forgets to clock out' questions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_attendance_review | Review one week of attendance for a site (or all sites) and draft a short manager summary. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema | Tables, definitions and caveats for the attendance data. |
TDQS
Scored across 7 tools
Tools are mostly distinct: individual late events, repeat-late rankings, missing-event lists, and repeat-missing rankings are clearly separated by purpose. The only minor overlap is employee_attendance, which could conceptually include late and missing incidents, but its employee-specific scope keeps it distinguishable.
There is a recognizable pattern among paired tools (repeat_late_arrivals / repeat_missing_clock_events), but naming style is mixed: list_locations and find_late_arrivals use verbs, while employee_attendance and location_trends are plain noun phrases. The inconsistency is not chaotic, but it is noticeable.
Seven tools is a well-scoped size for an attendance analytics server. Each tool covers a distinct query type without unnecessary redundancy or bloat.
The toolset covers the main attendance questions: site overview, individual late incidents, repeat-late rankings, per-employee summaries, location trends, missing clock events, and repeat missing-event rankings. For a read-only attendance analysis server, this feels complete with no critical dead ends.