docket

Invoices by status — e.g. the overdue ones (published, unpaid and past their due date: the invoice date plus the customer's or the workspace's payment term, as in docket's billing cycle) — optionally for one customer, with net and gross amounts. PMs and admins only.

list_invoices

Quotations by status — e.g. the ones sent to a customer and not confirmed yet — with net and gross amounts and totals. PMs and admins only.

list_quotations

The services (kinds of work, e.g. Design, Development) time can be booked with. Booking without one uses the user's default service.

list_services

The user's stopwatches: title, whether it runs, the time on the clock and the minutes a booking would suggest (rounded up to the next 15).

list_stopwatches

The user's time entries in a date range (default: the current week), with totals per day and per project. Admins may also ask for another user's or everyone's entries. Revenue only when the user may see it in docket.

list_time_entries

What's new for the user — docket's inbox: comments, mentions, assignments, closed or reopened tickets and document status changes, one entry per thing and event (with how many there were), newest first. Unread only unless asked otherwise.

my_notifications

What's on the user's plate: open tickets assigned to them, grouped by when they're planned — the Workload page's buckets: OVERDUE (ended before today), THIS_WEEK (lies in this week), THIS_MONTH, NEXT_MONTH, LATER, UNPLANNED (no dates). Default: overdue and this week.

my_tickets

How much the user has booked in a week (default: this week) against their working hours, day by day: which past days have gaps, and what they may have forgotten to book — open tickets assigned to them that are due by the end of the week, and tickets they commented on that week, without time booked on them that week.

my_week

Pauses one of the user's stopwatches; the time so far stays on it.

pause_stopwatch

Budget overview of projects — e.g. all of one customer — with how much of each budget is used and which are over budget. An amount budget counts the booked time's revenue and the external costs booked on the project; an hour budget the booked hours, and it is over budget too when its external costs top what the confirmed quotes sold. Basic users and up see the percentage and whether it is over; the budget itself (hours or money) only users who see it in docket; timetrackers see no budgets. Monthly budgets count the current month.

project_budgets

Details of one project: customer, status, deadline, open/closed tickets, progress (% of tickets closed) and how much of its budget is used. The budget itself only when the user may see it in docket.

get_project

One of docket's help articles in full, as Markdown, by its slug (from search_docs).

get_doc

Reopens a closed ticket (back to the board's backlog), as the reopen button in docket does — followers are notified.

reopen_ticket

Changes a ticket's start date, end (due) date and/or priority — e.g. moves it to next week. Pass only what changes; an empty string clears a date.

reschedule_ticket

Resumes a paused stopwatch of the user.

resume_stopwatch

The accounting forecast for a year, as on docket's Forecast page: per month the expected revenue and how much of it is paid, totals of confirmed quotations, invoiced amounts and external costs, and the quotations and invoices behind it — optionally for one customer. Net amounts. Admins only, as in docket.

revenue_forecast

Finds customers by company name. Returns ids for project_budgets, list_invoices and list_quotations.

search_customers

Finds projects the user can access, by name, number or customer. Without a query it lists active projects. Returns ids to use with the other tools.

search_projects

Searches docket's help articles (how docket works: time tracking, tickets, budgets, invoicing, Jira, AI connections, …) and returns the best matches with a snippet. Read one in full with get_doc.

search_docs

Finds tickets in projects the user can access — e.g. the ticket to book time on, or the user's own open tickets. Returns ids to use with the other tools.

search_tickets

Starts a new stopwatch for the user, running in parallel with any others. The ticket is optional — it can be picked when booking.

start_stopwatch

Who still has room in a week (default: this week), optionally only people with a given expertise (e.g. "Design", matched against their service and its category). Per person: target hours left this week from their working hours, open tickets assigned to them that are due by the end of the week, and — for users who see budgets — the remaining hour budgets of those tickets and the free hours that leaves. docket has no capacity planning, so this is an estimate from ticket budgets.

team_capacity

Details of one ticket: title, description text, status, priority, dates, assignees, its project — and the latest comments (newest first), to tell where it stands.

get_ticket

Returns the connected user (name, role, default service), the workspace, its country and the currency its amounts are in, today's date and time zone, and what this connection may do.

get_context