Get this business's name, timezone, working hours, price catalog, lead sources, and — most importantly — today's date plus the resolved YYYY-MM-DD ranges for "today", "tomorrow", "this week", "last week", "this month", "last month", and "this year" in the business's own timezone and week-start convention. Call this FIRST when a request involves any relative date, and pass the returned values to the dateFrom/dateTo arguments of the other tools rather than computing dates yourself. Also call it BEFORE creating a job, estimate, or line items: the returned catalog supplies the catalogItemId and price for each line, and jobSources lists the only accepted values for create_job's required source.

Fetch job records with filters. Use for any question about jobs, work performed, job types, job sources, or schedules. Returns raw job data - you calculate totals, counts, and comparisons.

Fetch payment records. Use for revenue questions, income tracking, payment history. Returns raw payment data - you sum and analyze.

Search or list customers. Use for customer lookups, finding contact info, or customer-related questions.

Fetch invoice records. Use for billing questions, unpaid balances, invoice status tracking.

Fetch estimates/quotes. Use for pending proposals, conversion tracking, estimate follow-ups.

Fetch line items from jobs (services/products sold). Use for questions about which items make money, most popular services, item profitability, catalog usage.

Fetch lookup tables: job types, job sources, catalog items. Use when you need to know what types/sources exist, catalog pricing, or to map IDs to names.

Get scheduled jobs, calendar events (time off, meetings, walkthroughs), and optionally available time slots. Use for 'what's on the calendar', 'when am I free', scheduling questions.

Schedule/create a new job for a customer. Pull the date and time from anywhere in the user's message, including pasted or forwarded text (e.g. 'scheduled for Wednesday the 24th at 9am'). Resolve relative dates like 'next monday' or 'the 24th' using the DATE REFERENCE in your instructions. Only ask for a date/time when none appears anywhere in the message — never re-ask for one the user already provided. If the customer is new (doesn't exist yet), pass their contact details here — do NOT call create_customer separately. This tool handles creating the customer AND the job in one step. When user says 'create customer X and schedule a job', use ONLY this tool.

Add a calendar event that is NOT a job: time off, a walkthrough, a meeting, a personal appointment, a block of time. Use this when the user says 'event', 'block off', 'time off', 'meeting', or describes something on the calendar that is not billable work. For scheduling billable work for a customer, use create_job instead. An event can optionally be linked to an existing customer and/or a crew member. Pull the date and time from anywhere in the message and resolve relative dates using the DATE REFERENCE.

Mark jobs as complete/done. ALWAYS use this tool when user wants to: close jobs, complete jobs, mark jobs done, finish jobs. Examples: 'close today's jobs', 'mark the Smith job done', 'complete yesterday's jobs'. Do NOT use get_jobs first - this tool finds and closes jobs in one step.

Change the date, time, or length of an existing job. Provide customerName (finds most recent scheduled job) OR jobId (exact match). Supply at least one of newDate, newTime, or durationMinutes. When moving the job, provide both newDate and newTime where possible. When the user only wants the appointment to block off more or less time (e.g. 'make Jon's appointment 3 hours', 'that job needs 90 minutes'), pass durationMinutes alone and leave the date and time out so the job stays where it is.

Cancel a scheduled job by setting its status to CANCELED. No data is deleted. Provide customerName (finds most recent scheduled job) OR jobId (exact match). Use customerName when user mentions a customer.

Add a new customer without scheduling a job. For new customers WITH a job, use create_job instead — it handles creating the customer inline. Extract ALL contact details the user provides (name, phone, email, address).

Create an estimate/quote for a customer. When the user specifies a flat rate or custom price (e.g. 'total $250', 'charge $300 flat'), pass lineItems with that custom unitPrice — do NOT use catalog pricing. Only fall back to catalog pricing when no price is specified. For flat rates, use a single line item with the service name and the stated price.

Add billable line items to an EXISTING job. Use when the user wants to add services/products to a job that's already scheduled (e.g., 'add a $50 cable management charge to the Smith job'). For brand-new jobs, use create_job with lineItems instead. Pass unitPrice when the user states a price; omit it to fall back to catalog matching by name.

Add a new service or product to the catalog with pricing. Use when user mentions pricing for services/products. This is the ONLY place to store pricing information.

Set or change how a customer found the business (their lead source). The source is stored on the customer, not on individual jobs, and every job they book counts toward it.