Matravo

View saved version →

---
name: matravo-rfq
description: Help the connected company's construction and landscaping materials B2B buyers and suppliers in Matravo find RFQs, quote requested lines, compare received offers, and save draft RFQs when explicitly requested.
---

# Matravo RFQs and offers

Use this skill for a signed-in Matravo company sourcing construction and landscaping materials through its B2B marketplace. The MCP server enforces company, role, plan, and sealed-bid access. These instructions do not grant access to other companies. General sector knowledge, consumer shopping, and invoice, email, accounting, or payment administration are outside this skill; answer or decline without calling marketplace tools.

1. **Find and inspect supplier opportunities.** Call `search-demands` for a supplier asking about published RFQs, with only the requested filters. For an “all” request, page from `page=1` through returned `totalPages` (maximum `pageSize=100`); report partial results if later calls fail. When the user gives an exact RFQ title, search with `text`, match the returned `title` exactly, and select only a unique result. Call `get-demand-detail` only with the `id` of a uniquely selected returned RFQ. Ask the user to select one if several match or no ID is available. Never guess an ID or infer competing bids from the sealed supplier view.
2. **Prepare and submit a supplier offer only on explicit request.** Verify the selected demand is published and open with a future `closingAt`, and check its currency, products and quantities. The supplier demand result does not expose the caller's role or plan; the server enforces role and entitlement on supplier tools. Treat successful calls as access for that action and stop on a returned denial; never infer entitlement from demand fields. Before writing, confirm the exact RFQ and requested unit prices with the user. For an Advanced RFQ whose product lines are returned, call `create-offer` once for that real `demandId`; it creates or returns the caller's own offer with pre-seeded lines. Proceed with pricing only if the returned offer is an editable Draft; do not retry or overwrite an already submitted offer. Match every returned `demandProductId` to the selected demand. Call `set-offer-line-price` once per requested line using the user's unit price in `unitPriceMinor` (for EUR, 85.00 means 8500). Never invent line IDs or prices. A Basic RFQ has no pre-seeded lines; ask for the required line details before using a different update flow, and do not pretend this granular pricing flow succeeded. Show the server-calculated total and terms. Call `submit-offer` only if the user explicitly requested submission and approves the exact offer and any host confirmation shown for destructive calls. Report Submitted only if the server returns that status. If a write result is uncertain, do not retry blindly.
3. **Compare buyer offers on one owned RFQ.** Call `list-my-demands` and select an `id` belonging to the connected buyer company. Pass that `id` as `demandId` to `get-my-demand-offers`; this reads one RFQ, not all company offers. Page through `totalPages` when asked for all offers, and report partial coverage after a page error. Compare only returned prices, delivery terms and statuses. An empty list or fewer than two bids cannot support a comparison. Never accept or award an offer unless the user separately requests an identified, authorized action.
4. **Save a buyer draft when requested.** Call `list-categories` and choose a returned selectable leaf `categoryCode`; do not pass a parent or invented code. Gather a title, description, ISO currency, delivery country, and future closing time. When the user wants a structured quantity and product line, choose `collectType=Advanced` and gather every required product name, positive quantity, and UN/ECE unit code; Basic ignores `products`. Call `create-demand` with `publish=false` and honor any host approval for the write. Report Draft only if returned. Do not call `publish-demand` or claim publication without a separate explicit request and confirmation.
5. **Handle access and tool failures.** For `SELLER_PACKAGE_REQUIRED`, `WEEKLY_OFFER_LIMIT_REACHED`, `BUYER_RFQ_LIMIT_REACHED`, or `MCP_RATE_LIMIT_EXCEEDED`, call `get-access-status` once with the returned error code as `barrier`. If not connected, ask the user to connect their Matravo account. Report other errors as returned; do not repeatedly retry a failed or rate-limited tool. Use `get-me` or `list-my-marketplace-offers` only when the user asks for their account or their own supplier offers.

Report only returned titles, statuses, dates, quantities, prices, totals, and access reasons. Keep buyer access to offers on their own RFQ separate from suppliers' sealed competing bids. Do not initiate payment or treat an unconfirmed draft or submission as complete.

Referenced files: 1 — file references are metadata, not package contents.