add_work_session_checkpoint
ChatGPTRecord an activity change or note now on your own running work session using server time. Read get_running_work_session first for sessionId and expectedVersion. For an activity change such as starting feeding, use kind activityChange and activity; for a note use kind note and note. The same work session continues: this never pauses time, deducts breaks or creates customer work. Retain the original arguments and idempotency key after uncertain outcomes.
attach_machine_repair_photo
ChatGPTAttach one user-provided photo to an existing open repair need. Requires a ChatGPT file input; never invent a file URL or accept an arbitrary website as evidence. JPEG, PNG and HEIC/HEIF, up to 5 MiB; HEIC conversion uses the existing Machine processor. Photo and reference are saved atomically. Download URLs are temporary, not stored; retry with the same file_id, operation key and expected version.
cancel_work_session
ChatGPTCancel your own running or completed unpaid work session after an explicit request to remove it. This stops a running timer and excludes the session from totals and payment selection. It preserves a locked cancelled record and audit history; there is no hard deletion or undo. Never cancel paid time: its payment marking must first be reversed by an administrator. For a running session, get_running_work_session provides sessionId and expectedVersion. Never guess a historical session ID or version. Retain the original arguments and idempotency key after an uncertain result.
complete_work_session
ChatGPTFinish the reviewed running session now. This also synchronizes linked customer work through the shared use case.
create_invoice_draft
ChatGPTCreate an editable EUR draft, not an issued or sent invoice. Use get_invoice_creation_options for saved seller/defaults. Ask for missing customer, price, VAT or agreed payment terms; never invent identity, bank details or tax treatment from addresses. Prices are NET excluding VAT even with showPricesWithVat=true. Incomplete drafts are allowed. Preserve arguments and idempotencyKey on uncertain retries. Show the saved draft before explicit approval to issue.
create_machine_repair_need
ChatGPTRegister an observed repair need on an explicitly identified company machine. Record the user observation without inventing a diagnosis or work performed. Example: water pump rattles. For an optional photo, first create the need, then use attach_machine_repair_photo with its returned ID/version. A repeated request must retain its original idempotency key.
create_receipt
ChatGPTRecord a completed direct sale and full payment actually received, only when authorized by the user. EUR prices INCLUDE VAT. No invoice or partial payments. Use get_receipt_options to resolve products and defaults; ask for missing price or required buyer information. Reuse the same idempotencyKey on every retry.
delete_invoice_draft
ChatGPTRemove an explicitly selected unissued draft only on user request, after get_invoice for current version. Preserves history; cannot remove an issued invoice or payment. Retain key and arguments on retry.
find_inventory_products
ChatGPTRead-only literal case-insensitive company-name search first. Catalog fallback occurs only on initial search with no company match; a company continuation never switches to catalog, even when empty. Return all candidates without guessed selection. Cursors bind company/query/source. Locations are separately paginated; do not assume a sole location while locationNextCursor exists. Source NONE permits helping define a new product; it does not create one. Use list_my_companies to resolve company; ask only if multiple relevant companies. Product discovery never imports or creates. Ask package size and count if amount missing; ask TOTAL versus PACKAGES for ambiguous 150g. For no relevant match, help define a new product with user-supplied package details; do not invent barcode, size or identity. Default searchSource=AUTO. If company candidates are irrelevant or the user explicitly chooses catalog search, set searchSource=CATALOG. Never select a product solely because its name contains the query. A non-exact or nearby product name MUST be confirmed with the user even when there is only one candidate (for example Premium Classic versus Premium Classic SX). Combine this question with missing size/count when useful. An exact product or ID already explicitly selected by the user requires no redundant confirmation. Never treat a single similar-name result as confirmed identity. An explicitly named alternative already approved by the user needs no further name confirmation when the stated condition is met (for example, use Premium Classic SX if that is the only match). This confirms product identity only, not missing quantity, package size, count or the receipt to reverse. Never guess or prefill a missing package count, including in a generated form. Leave an unknown count empty and require the user to supply it before receipt submission.
find_inventory_receipts
ChatGPTRead-only receipt history, newest first by creation time and UUID, optional exact product filter before pagination. Includes already-reversed receipts and their reversal IDs. Company/product/source-bound live cursors convey no authority. Product/location names are current labels, while movement identity, quantity and provenance remain original. Ask when the target receipt is ambiguous; never pick by name alone. Use this to locate a mistaken stock receipt without relying on conversation memory. Present original time, quantity, product, location and reversal state to disambiguate. Only RECEIPT entries can be reversed, not counts/transfers/issues. Never execute a reversal merely because one result is returned. A non-exact or nearby product name MUST be confirmed even for correction selection; never guess the original movement from a similar name. An explicitly named alternative already approved by the user needs no further name confirmation when the stated condition is met (for example, use Premium Classic SX if that is the only match). This confirms product identity only, not missing quantity, package size, count or the receipt to reverse. Require explicit user undo or correction intent. A technical timeout is not undo intent: retry the original operation with its original idempotency key first. Derive a concise reason such as mistaken receipt from the user's stated correction; do not ask an extra question just to phrase it when intent and movement are already clear.
find_machines
ChatGPTFind active company machines by name, manufacturer, model or serial number. Extract only the machine identity from a user report, e.g. John Deere 6320. Return all matching candidates across pages; do not silently choose among multiple machines. This tool never creates a machine.
find_unpaid_funded_documents
ChatGPTFind outstanding payer documents of third-party funded sales, including partial payments. For a complete invoice overview also call find_unpaid_invoices for ordinary invoices. Optional recipientQuery matches either payer or service recipient, so one farmer may match both funding and buyer obligations. Report payer, recipient, number, dueDate and balance; never count each payer document as a separate sale. Before payment, select automatically only if exactly one document matches and hasMore is false; otherwise ask which payer/document. Follow nextOffset until hasMore is false. Never record payment for a list-only question. Use today in Europe/Helsinki for relative dates.
find_unpaid_invoices
ChatGPTList issued sales invoices that are not fully settled, including partially paid invoices. For questions such as "what invoices are still unpaid", omit recipientQuery to list all recipients in the selected company. Optionally filter by recipient name. Follow nextOffset with the same company and filter until hasMore is false before claiming the list is complete; concurrent payments can change pages. Report recipient, invoice number, dueDate and remaining balance in EUR. Never register a payment merely because the user asks for a list. For a payment request, never silently select among multiple matches or a truncated result; ask which invoice. Use today and timeZone for relative dates.
get_invoice
ChatGPTRead current invoice/draft, totals, payment state and version. Read before updating, issuing or removing.
get_invoice_creation_options
ChatGPTRead saved seller, default receiving account, invoice preferences and today. Missing defaults must be supplied or configured; never fabricate them. Defaults do not prove VAT eligibility or agreed payment terms. Explicitly copy chosen values into a new draft; retain them on retries.
get_profile
ChatGPTReturn the Agriax account authenticated for this connection. Does not grant company membership or time permissions.
get_receipt
ChatGPTRead a receipt and authenticated PDF URL. The user must sign in to Agriax to download; this is not a public sharing link.
get_receipt_options
ChatGPTRead today, last payment method, default VAT and active products priced INCLUDING VAT. Search by query and follow nextOffset. Never silently choose between ambiguous products.
get_running_work_session
ChatGPTRead your own running work session and elapsedMilliseconds calculated at server observedAt. Use this to answer how long you have worked this session and obtain session ID/version before clocking out. No running session returns NotFound.
issue_invoice
ChatGPTIssue only an explicitly approved reviewed draft. Read get_invoice and show recipient, seller, rows, VAT, total and due date before approval to issue. Assigns legal number and freezes content/PDF; does NOT send or transfer money. Use reviewed expectedVersion. Keep original arguments/key on uncertain outcomes; never create a replacement invoice to recover from timeout.
list_machine_repair_needs
ChatGPTList repair occurrences for one exact machine, including closure history when requested. Read before resolving or attaching a photo; obtain the exact need ID and current version. Do not report repair completion from an observation alone.
list_my_companies
ChatGPTList all companies where the authenticated user currently has active membership, with their own role, employee reference and eligibility for own time reporting. Use before choosing a company for clock-in. If more than one company is eligible and the user has not selected one, ask which company; never choose the first arbitrarily. No eligible companies means clock-in is unavailable. This tool does not clock in or authorize a later write; permissions and employment must be checked again when acting.
list_receipts
ChatGPTList sales receipts and refunds. Follow nextOffset to get all pages.
receive_inventory_stock
ChatGPTReceive stock only after explicit product and amount intent. Reuse the same idempotencyKey for retries. Atomic product creation/catalog copy and RECEIPT. locationId or explicitly requested newLocationName are mutually exclusive. If both omitted, use the sole existing location only; otherwise require selection, never invent a location. Optional lot must belong to resolved company product. Current manager authority is required even on replay. All returned quantities are base-unit values. No partial local product/location/stock/receipt writes on failure. TOTAL requires amount and unit, forbids package fields/count. PACKAGES requires positive integral count and exactly one of selected packagingId or explicit packageSize/packageUnit. Selected packaging defines its size in product base units. Explicit size never mutates existing packaging. Positive quantities only; exact base-unit conversion must fit six decimals and existing stock range. Ask whether ambiguous 150g means total or package size; ask size and count when amount is absent. Explicit 2 packages of 150g needs no additional confirmation. If a catalog selection reuses a company copy, a selected packagingId must still represent the same exact physical size; changed or missing packaging returns 409 CatalogPackagingChanged and requires company-product discovery. Explicit totals/package sizes retain their user-specified meaning. A non-exact or nearby product name MUST be confirmed with the user even when there is only one candidate (for example Premium Classic versus Premium Classic SX). Combine this question with missing size/count when useful. An exact product or ID already explicitly selected by the user requires no redundant confirmation. Never treat a single similar-name result as confirmed identity. An explicitly named alternative already approved by the user needs no further name confirmation when the stated condition is met (for example, use Premium Classic SX if that is the only match). This confirms product identity only, not missing quantity, package size, count or the receipt to reverse. Never guess or prefill a missing package count, including in a generated form. Leave an unknown count empty and require the user to supply it before receipt submission.
refund_receipt
ChatGPTOnly on explicit authorization after money has been returned: create a full negative receipt linked to the original. No partial refunds. Reuse idempotencyKey on retries.
register_funded_document_payment
ChatGPTRecord actual received money for one reviewed third-party funded payer document; never initiate a bank transfer. Find unpaid funded documents first and resolve ambiguous payer matches. Omit amount to pay this payer document's remaining balance, not the total service value; specify amount for partial payments. Omit paidOn for today in Europe/Helsinki. Keep the key and every argument unchanged after uncertain outcomes. On revision conflict, refresh and review rather than blindly retrying with a new key. Creation of funded sales is not supported by MCP.
register_invoice_payment
ChatGPTRecord an actual received payment, not a bank transfer. First find the invoice. Select automatically only when exactly one match and hasMore is false; otherwise ask which invoice. Omitted amount pays remaining balance; omitted date uses today. Partial payments require amount. Preserve key and all arguments on uncertain outcomes. On VersionMismatch refresh and review; do not blindly repeat with another key.
resolve_machine_repair_need
ChatGPTMark an existing open repair need as resolved only when the user says it is fixed. Preserve its description and photos. Require a resolution note and the current version. Closure records server time and actor; it does not fabricate a performed service record, performer or performed date, and cannot be reopened.
reverse_inventory_receipt
ChatGPTReverse only an explicitly selected company RECEIPT. Current manager permission required even on replay. Append an exact opposite ISSUE at the same product/location/lot/unit and atomically store its immutable original link and idempotency response. Never delete or edit original history or product. A receipt may be reversed once across all actors/keys; another key after reversal returns 409 ReceiptAlreadyReversed. A non-RECEIPT returns 409 NotReversible. Negative resulting balances follow the existing ledger policy. No quantity or replacement identity is accepted. Use find_inventory_receipts when the target ID is not already explicit. Reuse the same idempotencyKey for retries. Ask for clarification if multiple receipts could match; do not invent or guess an ID. Successful reversal corrects stock only, leaving product/location and original history intact. A non-exact or nearby product name MUST be confirmed even for correction selection; never guess the original movement from a similar name. An explicitly named alternative already approved by the user needs no further name confirmation when the stated condition is met (for example, use Premium Classic SX if that is the only match). This confirms product identity only, not missing quantity, package size, count or the receipt to reverse. Require explicit user undo or correction intent. A technical timeout is not undo intent: retry the original operation with its original idempotency key first. Derive a concise reason such as mistaken receipt from the user's stated correction; do not ask an extra question just to phrase it when intent and movement are already clear.
start_work_session
ChatGPTClock in now for your own employment in the selected company, using server time. Never creates customer work. An existing running or overlapping session is rejected.
update_invoice_draft
ChatGPTReplace the COMPLETE editable draft after get_invoice. Replacement can discard existing fields or lines; no version-restore operation is available. Preserve fields not explicitly changed. On VersionMismatch read and review, never blindly overwrite. Issued invoices cannot be edited. Prices are NET excluding VAT. Retain original arguments/key on uncertain retries.
update_machine_repair_need
ChatGPTClarify or correct the description of an existing open repair need, for example which wheel has a puncture. Select the exact occurrence from list_machine_repair_needs and provide the complete intended description, retaining existing facts unless the user corrects them. Preserve status, photos, creation provenance and history. Require the current version and a stable idempotency key; never silently overwrite a revision conflict. Closed needs cannot be edited or reopened. Use resolve_machine_repair_need to mark a repair as fixed.
void_receipt
ChatGPTUse only on an explicit request to correct an erroneously issued sales receipt. Identify the exact receipt first and confirm the reason with the user if unclear. Creates a linked correction voucher without returning money. For an actual full refund use refund_receipt. Reuse idempotencyKey on retries.