Quarterline: Grease trap pumping for Austin restaurant groups, on one 90-day calendar

• describe_business — What Quarterline does (Grease trap pumping for Austin restaurant groups, on one 90-day calendar: Put every grease trap your Austin group runs on one board again
• submit_request — Send Quarterline a requirement (Grease trap pumping for Austin restaurant groups, on one 90-day calendar). Your board is recorded as a request and given a refer
• interpret_requirement — Give Quarterline the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which
• get_requirement — A Quarterline requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any
• edit_requirement — Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no
• send_requirement — Send the requirement to Quarterline once the buyer says to: the first send records the request (its receipt token is the requirement's token, for request_status
• request_status — Resume a requirement using the receipt credentials. Read the recorded requirement and any linked offers. Contact details are kept apart.
• inspect_offer — Read the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counter
• accept_offer — Place an order on terms you have inspected and the buyer has authorized you to accept. Requires the exact terms hash and explicit acceptance. Follow inspect_off
• decline_offer — Decline an issued offer on its inspected terms.
• release_payment — Confirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor.
• retrieve_deliverable — Retrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall. Before p
• counter_offer — Propose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price co
• submit_purchase_order — Send the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms. It is matched against the acc
• state_purchasing_requirements — Tell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which do
• report_vendor_status — Report the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and an
• inspect_delivery — Record the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a r
• answer_remedy — Accept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED). Recorded for the business, wh

No hidden text found in the tool definitions.

Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.