Red by Big Red Cloud

Create Quote

brc_create_quote

Creates a quote with a caller-supplied reference and reconciled product, VAT and Sales-analysis lines. Requires a valid routeToken issued for the matching action workflow. The token remains valid through lookup, preview and the permitted transaction. Placeholder tokens are invalid. A routeToken does not bypass preview or explicit-confirmation requirements. A call without confirmWrite: true returns confirmation_required and a payload preview. confirmWrite: true applies the previewed change after explicit confirmation. Passing preflight is not confirmation. Requires confirmCounterpartyExplicit: true; confirmation is scoped to the counterparty selected for the current preview.

Input Schema

TableJSON Schema

Name	Required	Description
`acCode`	Yes
`comments`	Yes
`ddNumber`	No
`poNumber`	No
`procDate`	Yes
`quantity`	Yes
`tranNote`	Yes
`companyId`	Yes	Required BRC company id for the quote payload. Use the connected company's id from existing records such as customers, products, or sales reps. Do not omit this field.
`entryDate`	Yes
`productId`	Yes
`reference`	No	Optional manual quote reference, max 6 characters. Required when quote references are manual, or when the quote reference setting is unknown. Quote reference must be 6 characters or fewer because Big Red Cloud truncates longer references.
`saleRepId`	Yes	Sales rep id from brc_list_sales_reps.
`unitPrice`	Yes
`vatRateId`	Yes
`vatTypeId`	No
`layoutType`	No
`routeToken`	Yes	Opaque routeToken from brc_route_request for this action workflow. Required for transactional tools. Routing permission only — does not replace preview-before-posting or confirmWrite.
`accountCode`	Yes	Sales Analysis account code for the quote product line, for example SA01.
`companyName`	Yes	Company context name, for example YOUR-COMPANY-NAME.
`productCode`	Yes
`saleRepCode`	Yes	Sales rep code from brc_list_sales_reps.
`confirmWrite`	No	Must be true only after a plain-English preview before posting 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. Nothing is written to Big Red Cloud until you confirm.
`connectionRef`	No	Opaque Red connection reference returned by brc_confirm_company_connection. Pass this exact value on every later tool call when the MCP client rotates session ids (for example Vibe/Mistral). Keep reusing the same connectionRef after successful tool calls — do not start a new connection because a lookup returned empty or partial data. It is not an API key and does not contain credentials.
`vatPercentage`	Yes
`customerOwnerId`	Yes
`customerOwnerName`	Yes
`analysisCategoryId`	Yes
`confirmCrAnalysisCategory`	No	Set true only after the user confirms a CR sales analysis account code is intentional for this product line.
`confirmCounterpartyExplicit`	No	Must 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 preview, was inferred from context, or was filled in without the user's explicit choice in this conversation.
`confirmQuotesAutoGenerateInBrc`	No	Set 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.

TDQS

A4.1/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing that a call without confirmWrite:true returns confirmation_required with a payload preview, that preflight is not confirmation, and that a routeToken does not bypass preview or explicit-confirmation requirements. It also clarifies the scope of confirmCounterpartyExplicit, which is highly non-obvious behavior.

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 front-loaded with the purpose and then logically progresses through token requirements, preview behavior, and confirmation constraints. It is dense but focused; slight redundancy with schema-level descriptions is acceptable given the transactional 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?

For a 30-parameter transactional tool with no output schema and sparse schema coverage, the description covers the highest-risk operational aspects: routeToken validity, preview-before-posting, explicit confirmation, and counterparty confirmation scoping. It does leave gaps in how the many required fields interrelate and what a successful response looks like, but the core call sequence is well specified.

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

Parameters2/5

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

Schema description coverage is only 40%, so the description must compensate, but it only partially does. It groups product, VAT, and Sales-analysis fields into reconciled lines and explains routeToken/confirmWrite semantics, yet most required parameters such as customerOwnerId, acCode, entryDate, procDate, saleRepId, and similar fields receive no meaningful descriptive help beyond their raw names.

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

Purpose5/5

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

The opening sentence names the exact operation ('Creates a quote') and specifies a 'caller-supplied reference' and 'reconciled product, VAT and Sales-analysis lines.' This clearly distinguishes the tool from its auto-reference sibling brc_create_quote_gen_ref and from other create_* tools.

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

Usage Guidelines4/5

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

The description provides clear invocation context: a valid routeToken for the matching action workflow is required, and the two-phase preview/confirmWrite flow is explained. It does not explicitly name alternatives or exclusions, but the caller-supplied reference trait implies when this tool, rather than the generated-reference variant, is appropriate.

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

All Red by Big Red Cloud tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation4/5

Most tools have a clear single resource-and-action focus, and the systematic naming helps an agent separate create/get/update/delete/list operations. The main confusion risks are the help/search cluster (red_help, find_help_resources, get_help_resource_details) and the payment/cash-payment/batch-payment variants, which require careful reading of the descriptions to avoid misselection.

Naming Consistency4/5

The brc_ prefix with snake_case verb_noun naming is used consistently across the vast majority of tools, e.g. brc_list_customers, brc_create_sales_invoice, brc_delete_purchase. A few noun-style names like brc_company_readiness_check, brc_grouped_nominal_accounts_report, and brc_red_help break the pattern, but these are minor deviations.

Tool Count1/5

159 tools is an extreme count for an MCP server, well beyond the 50+ threshold described as an extreme mismatch. While the accounting domain is broad, the surface is inflated by batch variants, generated-reference variants, and without-dormant list variants that could be consolidated.

Completeness4/5

Core accounting entities have strong lifecycle coverage: customers, suppliers, products, sales reps, bank accounts, quotes, sales invoices/entries/credit notes, purchases, payments, cash receipts, accruals, prepayments, and nominal journal batches all support relevant CRUD and batch operations. Minor gaps include the quote update being limited to the reference only, no update/create tools for VAT categories or company settings, and email sending being limited to quotes, invoices, and statements.

Create Quote

Input Schema

TDQS

Glama MCP Gateway

TDQS

Resources