tallied

Use this when the user asks to invoice a client, bill for a period, or turn unbilled hours into an invoice. Creates a draft only; nothing is sent and the client cannot see it yet. Includes all unbilled billable entries for the client through through_date and marks them as invoiced. Show the draft to the user, then use invoice.send when they ask to send it.

Use this when the user asks about a specific invoice's lines, total, due date, payment link, or payment status. Accepts an invoice id or number (e.g. "INV-0007"). Renders an invoice preview.

Use this when the user asks about invoices: outstanding, overdue, paid, drafts, sent this month, which clients owe money, or a specific client's invoices. Returns invoice summaries with status and totals. Use invoice.get for line items.

Use this when the user asks what they could invoice a client for, or wants to see unbilled work before creating an invoice. Creates nothing. Returns the lines, hours, and total an invoice.create_draft call with the same arguments would produce.

Use this when the user says a client paid by check, bank transfer, cash, or otherwise outside the Stripe payment link. Marks the invoice paid. Stripe payments are recorded automatically; do not use this for them.

Use this only after the user has reviewed the draft and asks to send it. Emails the invoice with a Stripe payment link to the client's billing email (or to_email) and changes the status to sent. Do not call to re-send unless the user asks. This sends a real email to a real person.

Use this only when the user explicitly asks to void or cancel an invoice. Requires confirm: true; without it returns the invoice for a final check. Voiding releases its time entries so they can be invoiced again. Paid invoices cannot be voided.

Use this only when the user explicitly asks to remove an entry. Requires confirm: true; when omitted it returns the entry for a final check without deleting. Entries on sent invoices cannot be deleted. To fix a mistake, prefer time.update_entry.

Use this when the user asks what they worked on, what they logged, or wants entries for a day, week, project, or client. Returns individual entries with resolved project/client names and per-entry rates. For totals and breakdowns use time.report instead. Do not use for calendar events, tasks, or reminders. Defaults to the current week in the workspace timezone.

Use this when logging multiple entries at once: an end-of-day recap, a pasted list, or after time.propose_entries has been confirmed. Each entry is validated independently; partial success is reported per row with the same statuses as time.log_entry. Do not call before the user has confirmed proposed entries.

Use this when the user states work they did with a duration or a start and end time, for today or a past date. Do not use for future plans, reminders, timers, or calendar scheduling. If the project is ambiguous this returns candidates instead of logging; ask the user and retry. Never auto-creates a project. Echoes the parsed duration and resolved date so you can confirm.

Use this when the user wants to reconstruct or catch up a day or week from calendar events, commits, pull requests, tickets, or notes you have already gathered from other tools or the user. Pass the raw activity; this returns proposed entries mapped to the user's projects with confidence scores, plus unmatched items, detected gaps, and overlaps. It saves nothing. Present the proposal, confirm with the user, then call time.log_entries_batch with the confirmed entry objects. Do not use for logging a single known entry (use time.log_entry).

Use this when the user asks how many hours they worked, billable vs. non-billable, hours by day, project, or client, or how much is unbilled. Returns aggregates, not individual entries (use time.list_entries for those). Defaults to the current week in the workspace timezone. With group_by "day" this renders a week grid.

Use this when the user corrects a duration, description, project, date, times, tags, or billable flag on an existing entry. Requires the entry id (from time.list_entries or a previous log result). Cannot edit entries already on a sent invoice; returns an error explaining why. Returns the previous and updated entry.

Use this when the user names a client that does not exist and confirms it should be created, or asks to add a client with a rate or billing email. Do not create clients speculatively while logging time; ask first. Free plan allows one client; the error includes upgrade_url when the limit is hit.

Use this when the user names a project that does not exist and confirms it should be created, or asks to add one with a rate. Aliases help future fuzzy matching ("acme site", "landing page"). Do not create projects speculatively; ask first.

Use this when the user asks what projects or clients exist, what a rate is, or when you need to resolve an ambiguous project name before logging time. Returns clients with their projects, aliases, and effective rates. Cheap to call. Prefer reading the workspace://context resource once if the host supports resources.