Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Changed the definition of "request_status"
Resume a requirement using the receipt credentials. Read the recorded requirement, any replies the business has published on it (messages: where it answers a buyer with no email, it answers here) and any linked offers. Answer a reply by sending a continuation. Contact details are kept apart.
Added "edit_requirement", "get_requirement", "interpret_requirement" and 1 more (14 tools before, 18 now)
Change a requirement by field — Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value.
Read a requirement as it stands — 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 offer on it.
Describe a need to Quarterline in words — 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 words it came from), conflicting or unclear facts come back as one question, and words not yet read are kept as written. Pass the requirement (id, token) from the first answer to continue it. Nothing is sent or ordered: send_requirement sends it when the buyer says so. When you already have the fields in structured form, use submit_request instead.
Certificate recorded, valid to 2027-02-05
Authorization not required
Added "answer_remedy", "counter_offer", "inspect_delivery" and 3 more; changed the definition of "accept_offer", "decline_offer", "describe_business" and 5 more (8 tools before, 14 now)
acceptAccept an offer and place the order
⟨7 unchanged words⟩ ,"type":"boolean"},"id":{"description":"The request or offer id from your receipt or customer link","format":"uuid","pattern":"^([0-9a-fA-F ⟨74 unchanged words⟩
Unknown → Live
First tool surface recorded: 8 tools (server version 1)
https://quarterline.forevenza.com/mcp (mcp_streamable_http) — from mcp_registry, with the record
Showing the latest 8 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
Send the 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 and offers); a later send of a changed requirement records a revision of the same request. Name the revision the buyer saw. This orders nothing: an offer comes later and is accepted separately on its exact terms.
declineDecline an offer
{"$schema":"http://json-schema.org/draft-07/schema#","properties":{"id":{"description":"The request or offer id from your receipt or customer link","format":"uuid","pattern":"^([0-9a-fA-F ⟨60 unchanged words⟩
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 against the City's 90-day ceiling, and request one calendar for all locations, one invoice and the manifests filed per location.), what happens to a request, what you receive, its scope, and the requestfields.fields with examples.
inspectInspectofferan offer's terms and thread
⟨5 unchanged words⟩ terms hash, order state and processor paymentlinks.links, and the thread the business published on the offer: its answers to counteroffers (thread.counteroffers), the purchasing requirements, vendor status and purchase order matches it holds (thread.purchasing), and the portions, shortfall and remedies of delivery (thread.fulfilment). Use the offer link credentials, or credentials ⟨8 unchanged words⟩
{"$schema":"http://json-schema.org/draft-07/schema#","properties":{"id":{"description":"The request or offer id from your receipt or customer link","format":"uuid","pattern":"^([0-9a-fA-F ⟨46 unchanged words⟩
releaseRelease a payment condition
⟨7 unchanged words⟩ ,"type":"boolean"},"id":{"description":"The request or offer id from your receipt or customer link","format":"uuid","pattern":"^([0-9a-fA-F ⟨67 unchanged words⟩
Check a requeststatusand its offers
{"$schema":"http://json-schema.org/draft-07/schema#","properties":{"id":{"description":"The request or offer id from your receipt or customer link","format":"uuid","pattern":"^([0-9a-fA-F ⟨46 unchanged words⟩
retrieveRetrieve a paid order's deliverable
{"$schema":"http://json-schema.org/draft-07/schema#","properties":{"id":{"description":"The request or offer id from your receipt or customer link","format":"uuid","pattern":"^([0-9a-fA-F ⟨46 unchanged words⟩
Send Quarterline a requirement
Send Quarterline a requirementto(GreaseQuarterline.trapItpumpingisforkeptAustinwithrestaurantagroups,referenceonnumber.one 90-day calendar). Your board is recorded as a request and ⟨86 unchanged words⟩ terms. Contact details are deleted after 180 days. It is answered with a receipt: keep its id and token to read its status (request_status), to add details later (continuation) and to act on an offer made in reply. A requirement is not an order and costs nothing.
⟨44 unchanged words⟩ ,"type":"object"},"continuation":{"description":"The receipt id and token of an earlier request, to add to it instead of opening a new one","properties":{"id":{"format":"uuid" ⟨49 unchanged words⟩ ,"type":"object"},"need":{"description":"The requirement in the buyer's own words","maxLength":2000,"type":"string"},"quantity ⟨22 unchanged words⟩ "array"},"specifications":{"additionalProperties":{},"description":"Fields from the request_schema describe_business returns","propertyNames":{"type":"string"}," ⟨22 unchanged words⟩
Answer a proposed 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, which applies it and shows the result there. Accepting a credit or refund here moves no money; the business records it when its payment processor does.
Propose changes to an 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 companies), a delivery date, a total price for the whole, a payment plan, or a note. It is a proposal, not a change: the terms stand and can still be accepted as they are. The business answers it in inspect_offer thread.counteroffers, with a revised offer to inspect and accept, or a reason. A later proposal replaces an earlier one still awaiting an answer. Nothing here orders or pays.
Record a delivery inspection — 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 rejection, optionally for one portion of the order. Whether it was accepted is computed: only when nothing is rejected. Recorded for the business, which answers a rejection in inspect_offer thread.fulfilment, with a proposed remedy. Nothing here pays or refunds.
Report vendor approval 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 any documents requested. Recorded as the buyer's own statement; the business answers it in inspect_offer thread.purchasing.
State the buyer's 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 documents are needed, the seller's vendor id with the buyer, where orders and invoices go, and the payment terms. Recorded as the buyer's statement; the business answers it in inspect_offer thread.purchasing. Nothing here orders or pays.
Send a 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 accepted terms; differences are recorded and shown in inspect_offer thread.purchasing as exceptions, never silently accepted. A changed purchase order is the same number with a higher revision. This does not accept the offer and pays nothing.