Handoff

Use this tool when the user asks to create or update Handoff business records and the operation is reversible. Use handoff_read first to discover the exact operation and arguments. This tool rejects reads and destructive or irreversible actions. Handoff reversible write commands. Use handoff_read first to discover operations and arguments. • call <tool> <json-args> Run a non-destructive create or update operation. • api <METHOD> <path> [<json>] Run an endpoint that changes state but is not destructive. Use handoff_action instead for deletes, sends, approvals, rejections, revocations, and other irreversible actions.

handoff_write

Use this tool when the user explicitly asks to perform a destructive or irreversible Handoff action, such as deleting, sending, approving, rejecting, revoking access, or rematching a catalog. Use handoff_read first to discover the exact operation and arguments. This tool rejects reads and reversible writes, and requires confirm:true for destructive execution. Handoff destructive or irreversible action commands. Use handoff_read first to discover operations and arguments. • call <tool> <json-args> Run a destructive catalog operation. • api <METHOD> <path> [<json>] Run a destructive endpoint directly. Deletes, proposal and invoice actions, vendor-portal access changes, time-entry approval/rejection, and estimate-catalog rematching require "confirm": true in the args.

handoff_action

The user's Handoff account data. Handoff is a construction estimating & project-management product; this tool reads the user's own Handoff projects, estimates, proposals, invoices, contacts, daily logs, documents, and expenses, and discovers available operations. USE THIS TOOL whenever the user asks about their Handoff data or mentions 'Handoff', 'my projects', 'my estimates/proposals/invoices/clients/contacts', or wants to find or list any of the above. This is NOT an issue tracker, code repository, or engineering project board — do not confuse the user's Handoff business records with Linear/Jira/GitHub 'projects'. When in doubt for anything Handoff-related, prefer this tool. Whenever the user asks to work with one of the features below, FIRST run `context <feature>` to see its tools and their arguments, THEN `call <tool> {...}`. Use `search <regex>` if the feature isn't obvious, or `api <METHOD> <path>` to reach any endpoint directly. Features: • activities (2) • business-advisor (2) • catalog-rates (2) • catalogs (6) • comments (4) • contacts (6) • daily-logs (6) • documents (7) • estimate-generations (1) • estimates (24) • expenses (4) • files (7) • hooks (3) • invoice-payments (2) • invoices (9) • me (1) • projects (22) • proposals (9) • schedule-phases (2) • suppliers (5) • templates (2) • time-tracking (8) • triggers (6) --- Handoff read and discovery commands. The feature overview is always above — no need to fetch it. • context <feature> List a feature's tools, each with its arg summary. e.g. context estimates • search <regex> Find a tool by name/description across features. e.g. search invoice • call <tool> <json-args> Run a read-only catalog tool. Args: {pathParams?, query?} e.g. call get_projects_by_id {"pathParams":{"id":"<uuid>"}} • api <METHOD> <path> [<json>] Run a read-only endpoint directly. json: {query?, body?} e.g. api GET /contacts {"query":{"limit":5}} Use handoff_write for reversible changes and handoff_action for destructive or irreversible actions.

handoff_read