B2 Portal

Applies one version-checked set of typed actions to a B2 Portal RFQ draft and returns state APPLIED. Provide the latest target unchanged, use type as the action discriminator, include reason plus 1-5 evidence strings, and send only keys allowed by that action variant. SEND_AS_CUSTOM_LINE uses exactly type, decisionId, decisionUpdatedAt, unitPrice, reason, evidence; do not add description or quantity. CORRECT_LINE_ITEM rebuilds the line decision, so read the latest RFQ context afterward and apply the requested QuickProduct, custom-line price, catalog-gap, or review action to the replacement. RESOLVE_CUSTOMER_REVIEW uses exactly type, correction, reason, evidence. Directory IDs are canonical decimal strings; convert their digits exactly to positive safe integers for coreBridgeAccount.customerId and coreBridgeContactId, without rounding or inference. For an order-backed CUSTOMER_CONFIRMATION, use customer.mode existing_customer with the exact authorized local customer ID when retaining or replacing a local record. When search_contacts returns an existing CoreBridge contact, use contact.mode corebridge_contact with its exact coreBridgeContactId. Use contact.mode existing_contact only for the authorized local contact row and include its current coreBridgeContactId when retaining a known binding. A selected CoreBridge account plus a selected or new account-scoped contact can materialize the replacement local record. Use customer.mode new_customer only for pre-order MISSING_CUSTOMER. This tool changes only the B2 Portal draft; it never pushes to CoreBridge.

apply_rfq_draft_actions

Creates an RFQ intake from notes and up to five prepared attachment references in one authorized CoreBridge V2 location. Prepare one upload session for each file, complete the signed-in upload page or certified adapter transfer, then pass each returned attachment object unchanged with the same requestId. The intake enters B2 Portal's extraction and operator-review workflow; it is not pushed to CoreBridge.

create_rfq_from_notes

Returns the authorized CoreBridge V2 locations, forwarding addresses, attachment limits, and operator-review boundary for a new B2 Portal intake workflow. Use this when starting an intake. It does not change an RFQ or push to CoreBridge.

get_intake_context

Returns one RFQ-scoped customer workflow: extracted identity, B2 Portal's current local operational record and binding, and authoritative CoreBridge account/contact candidates. These are not competing customer lists. A resolved order-backed CUSTOMER_CONFIRMATION remains readable so the caller can present alternatives and explicitly amend the draft. Use customer.mode existing_customer with the exact authorized local customer ID when retaining or replacing a local record. To select a CoreBridge account, search it here and then request its contacts; a selected or new account-scoped contact is materialized as the replacement local record. Use coreBridgeAccount.mode create_new only when the account is genuinely missing. customer.mode new_customer is valid only for a pre-order MISSING_CUSTOMER review. This tool never mutates data.

get_rfq_customer_resolution

Checks an RFQ intake created by this MCP connection. A signed-in B2 Portal review URL is returned only after a specific RFQ or review target exists. It does not return customer message content and cannot push to CoreBridge.

get_rfq_intake_status

Compatibility alias for get_rfq_review_context. Reads the same normalized V2 review state and is read-only. New integrations should use get_rfq_review_context.

get_rfq_triage_context

Returns one active QuickProduct and one bounded page of its nested parts, dimensions, material fields, restrictions, price provenance, and versions from B2 Portal's synchronized V2 catalog. Continue with nextPartCursor until it is null. Use only an ID returned by a catalog or RFQ review tool.

get_v2_quickproduct

Reads the normalized V2 review state for customer, commercial-document, bundle, and every line-item blocker. Candidate products are hydrated with catalog evidence and exact versions. When coreBridgePushAllowed is true, present the complete final RFQ summary and obtain explicit operator approval before using push_rfq_to_corebridge with the returned pushTarget unchanged.

get_rfq_review_context

Lists one bounded page of active QuickProducts from B2 Portal's synchronized CoreBridge V2 catalog. Continue with nextCursor until it is null, then use get_v2_quickproduct for complete parts. Cursors are tied to this connection, location, page size, and catalog generation.

list_v2_quickproducts

Creates a retry-safe, short-lived, tenant-scoped upload session for one standalone chat attachment or other PDF, image, Word, or PowerPoint file that is not being forwarded as an original email. Use one stable idempotencyKey for that exact file preparation. The file bytes are transferred outside MCP JSON; never encode them into MCP JSON. The response includes a signed-in upload page, certified-adapter multipart fields, and an attachment reference; a signed-in operator completes the upload page, and only a certified adapter transfers through the multipart fields. Reuse the same requestId for up to five files and create_rfq_from_notes, and pass each returned attachment object unchanged.

prepare_rfq_attachment_upload