blok-berichtsheft
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weekA | Read the Berichtsheft (training log) entries for the week containing the given date, including each day's location, presence, logged activities with hours, and the week remarks. |
| add_activityA | Add a new Berichtsheft activity entry for a specific day. Reuses an empty row if one exists for that day, otherwise adds a new row. Optionally also sets that day's location and/or presence status. |
| set_day_statusA | Set the location and/or presence status for a specific day in the Berichtsheft, without adding an activity. |
| list_departmentsA | List the valid "Abteilung/Sparte" codes for this account (the same autocomplete list BLok itself offers). Call this and ask the user which one applies before calling set_department or add_activity with a department - do not guess a code. |
| set_departmentA | Set the "Abteilung/Sparte" field for the week containing the given date. Call list_departments first and confirm the code with the user rather than guessing. |
| set_week_remarksA | Set the free-text remarks ("Bemerkungen") for the week containing the given date. |
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 operation: reading a week, adding an activity, setting day status, listing departments, setting department, and setting week remarks. There is no functional overlap.
All tools follow a consistent verb_noun pattern (e.g., get_week, add_activity, set_day_status), making the API intuitive and predictable.
With 6 tools, the server is well-scoped for managing a training log (Berichtsheft). Each tool serves a clear purpose without redundancy or deficiency.
The core workflow (read week, add activity, set status/department/remarks) is covered. However, there is no explicit update or delete operation for activities, which could be a minor gap.