Skip to main content
Glama
BigRedCloud

Red MCP Server

Official
by BigRedCloud

brc_create_quote

Create a BRC quote with structured fields, requiring sales rep, analysis category, and explicit user confirmation for counterparty and write operations.

Instructions

Creates a BRC quote using structured MCP fields. Requires a quote reference when quote references are manual or unknown. Do not use when Quotes reference setting is Unknown unless the user has provided a quote reference. Draft previews include a Missing or not provided section for blank customer phone or email only — warnings only, do not invent values. Requires saleRepId and saleRepCode. Do not use default or demo sales rep values. If missing, list sales reps or ask the user to choose one before creating. Requires analysisCategoryId and accountCode from a Sales Analysis category on each product line. Do not default to CR01/Customer or the first listed category. Set confirmCrAnalysisCategory=true only after the user confirms a CR account code is intentional. First call without confirmWrite: true returns confirmation_required and a payload preview — show a plain-English draft in chat, then retry with confirmWrite: true only after explicit user confirmation in a later message. Passing preflight is not confirmation. Also requires confirmCounterpartyExplicit: true once the user has explicitly named or confirmed the customer/supplier in the current conversation. Do not reuse a counterparty from an earlier draft without that confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
acCodeYes
commentsYes
ddNumberNo
poNumberNo
procDateYes
quantityYes
tranNoteYes
companyIdNoOptional BRC company id used in quote payload. Defaults to previous test company id if omitted.
entryDateYes
productIdYes
referenceNoRequired when quote references are manual, or when the quote reference setting is unknown.
saleRepIdYesSales rep id from brc_list_sales_reps.
unitPriceYes
vatRateIdYes
vatTypeIdNo
layoutTypeNo
accountCodeYesSales Analysis account code for the quote product line, for example SA01.
companyNameYesCompany context name, for example YOUR-COMPANY-NAME.
productCodeYes
saleRepCodeYesSales rep code from brc_list_sales_reps.
confirmWriteNoMust be true only after a plain-English draft has been shown in the current conversation and the user explicitly confirmed posting (for example yes, create it / post it now / confirm). Never set true on the first call or because the user initially asked to create something.
vatPercentageYes
customerOwnerIdYes
customerOwnerNameYes
analysisCategoryIdYes
confirmCrAnalysisCategoryNoSet true only after the user confirms a CR sales analysis account code is intentional for this product line.
confirmCounterpartyExplicitNoMust be true only after the user explicitly named or confirmed the customer, supplier, or other counterparty in the current conversation. Never set true because a customer or supplier appeared in an earlier draft, was inferred from context, or was filled in without the user's explicit choice in this conversation.
confirmQuotesAutoGenerateInBrcNoSet true only after the user confirms quotes are auto-generated in Big Red Cloud. Required for brc_create_quote_gen_ref when Quotes reference setting is Unknown.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, but the description fully discloses behavioral traits: requires saleRepId and saleRepCode, requires analysisCategoryId and accountCode, warns against defaulting to CR01/Customer, describes the confirmation_required preview, and mandates explicit user confirmations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but densely packed with essential instructions. Every sentence adds value, though it could be slightly more structured (e.g., bullet points) for easier scanning. It is appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 28 parameters, no output schema, and no nested objects, the description is fairly complete. It covers the confirmation flow, prerequisites, and constraints. Missing explicit mention of success response structure, but the agent can infer from the confirmation flow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (36%), so the description carries the burden. It clearly adds meaning for critical parameters like confirmWrite, confirmCounterpartyExplicit, confirmCrAnalysisCategory, and the reference parameter. However, not all 28 parameters are explicitly described in the main description, but key ones are covered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it creates a BRC quote using structured MCP fields. It distinguishes from sibling tools like brc_create_quote_gen_ref by detailing quote reference requirements. However, it could explicitly name the sibling for contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides extensive usage guidance: when to require a quote reference, not to use with unknown settings unless reference provided, do not use default sales rep values, requires explicit user confirmations for write, counterparty, and analysis category. It even specifies the two-step confirmation workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BigRedCloud/red-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server