Timebook
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMEBOOK_API_URL | No | Override the API host (useful for self-hosted Timebook or local dev) | |
| TIMEBOOK_WEB_URL | No | Override the web host (useful for self-hosted Timebook or local dev) |
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 |
|---|---|
| whoamiA | Return the currently authenticated Timebook user (id, email, name). |
| list_projectsA | List all projects available to the current token. Returns id, name, and client for each project. |
| list_clientsA | List all clients available to the current token. |
| get_active_timerA | Return the currently running timer (project, description, started_at), or null if no timer is running. |
| start_timerA | Start a timer on a project. Stops any other running timer first — Timebook allows only one active timer at a time. |
| stop_timerA | Stop the currently running timer. Returns { stopped: false } if no timer was running. |
| log_timeA | Log a manual (past) time entry. Provide either |
| list_entriesA | List recent time entries, optionally filtered by project and/or date range. Returns at most 50 entries by default; pass a higher |
| update_entryA | Edit one or more fields on an existing time entry. Any combination is valid; unset fields are left as-is. Server-enforced authorship rule: this token can only edit entries it created itself (sessions and admins bypass). |
| delete_entryA | Delete a time entry. Server enforces: not invoiced, and either this token created it or the caller is an admin / web session. |
| create_clientA | Create a client (the person/company you bill). Needed before any project or time entry can exist. Typical first step on a fresh account. |
| create_projectA | Create a project under a client. Time entries are always tracked against a project. Typical second step on a fresh account, after create_client. |
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 12 tools
Each tool targets a distinct action and resource. For example, create_client is clearly different from start_timer, and list_clients is separate from list_projects. There is no ambiguity between tools.
All tool names follow the imperative verb_noun pattern (e.g., create_client, delete_entry, stop_timer). The only exception is whoami, which is a common standalone command but still consistent with the overall style.
12 tools cover the essential operations for a time tracking service: client and project management, time entry CRUD, timer control, and user info. This is a well-scoped set without excess or deficiency.
The tool set covers the core lifecycle: create and list clients/projects, log and update time entries, and timer operations. Minor gaps like missing update/delete for clients and projects suggest room for improvement, but the core workflow is complete.