woffu-manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WOFFU_TZ | No | Office time zone, IANA name, default Europe/Madrid | |
| WOFFU_HOST | Yes | Your Woffu domain, e.g., yourcompany.woffu.com | |
| WOFFU_TEAM | No | Default team for get_team_availability if different from your own | |
| WOFFU_PASSWORD | Yes | Your Woffu password (used only once to request a token, never stored) | |
| WOFFU_USERNAME | Yes | Your Woffu login email |
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 |
|---|---|
| get_time_off_balanceA | How much time off the user has left, per bucket: holidays, paid leave, calendar adjustment hours, and so on. Each entry carries its own unit — some buckets count days and others hours, so never add them together. Every bucket also carries |
| list_holidaysA | The public holidays ahead on the user's work calendar, roughly a year out. Useful for planning time off: a holiday costs no days from any bucket, and one next to a weekend makes a long weekend. |
| get_team_availabilityA | How many days each person on the team is available over a date range, and how many they are off. Built for capacity planning: a PO sizing a sprint needs to know who is away before committing to a load. Per person: |
| list_time_off_requestsA | The user's time-off requests (holidays, leave...) with their status: pending, approved or denied. Omit |
| request_time_offA | Files a time-off request in Woffu. WRITES to the user's record and their manager sees it. |
| edit_time_off_requestA | Changes the dates, times or comment of an existing request. WRITES to Woffu. |
| cancel_time_off_requestA | Withdraws a time-off request. WRITES to Woffu: a pending request is deleted outright and the balance it held is returned. |
| list_pending_daysA | Workdays with no hours logged in Woffu, each with the exact time ranges that would be clocked in. Excludes weekends, holidays, absences (leave, adjustment days, sick leave), days already clocked in, and days Woffu will not let the user edit. Read-only. |
| clock_in_daysA | Clocks the given days in Woffu. WRITES to the user's official timesheet. Requires an explicit list of dates: there is no "clock in everything". Before calling this, show the user the dates and their time ranges (from list_pending_days) and get their confirmation. By default each day uses the theoretical schedule Woffu itself proposes, which is almost always what the user wants. Only pass |
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 9 tools
Each tool targets a distinct action (cancel, clock in, edit, get availability, get balance, list holidays, list pending, list requests, request) with no overlap. An agent can easily differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., cancel_time_off_request, list_holidays), making them predictable and easy to remember.
Nine tools is a well-scoped set for a time-off and attendance manager, covering essential operations without unnecessary bloat.
The toolset covers core CRUD for time-off requests, clock-in for pending days, and support data (holidays, balances). Minor gaps exist: no ability to view past clocked days or edit clock-in entries, but the main workflows are supported.