Skip to main content
Glama
loldwyer

Red MCP Server

by loldwyer

brc_create_quote

Create a Big Red Cloud quote requiring explicit user confirmation of sales rep, analysis category, and counterparty; returns a draft preview for review before posting.

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 were provided, so the description fully bears the burden of behavioral disclosure. It reveals many traits: draft previews include Missing sections for blank phone/email, warnings only; first call without confirmWrite returns confirmation_required with a payload preview; requires explicit user confirmation for write, counterparty, and CR analysis category; and warns against inventing values. This is comprehensive for a mutation tool.

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 long (multiple sentences) but every sentence adds value. It is front-loaded with the core action and then lists important constraints. It could be slightly restructured for readability, but it avoids fluff. The density is justified by the complexity of the tool.

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 (18 required) and no output schema, the description is very complete. It covers the multi-step creation flow, required preconditions, and explicit confirmation flags. It lacks details on return values (no output schema) but that is acceptable. Overall, it provides enough context for an agent to use the tool correctly.

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%), and the description adds significant meaning beyond the schema. It explains the purpose of confirmWrite, confirmCounterpartyExplicit, and confirmCrAnalysisCategory with usage rules. It also clarifies that reference is required when manual/unknown, and warns against defaulting analysisCategoryId. While not every parameter is explained, the critical ones are well-covered, compensating for the schema gaps.

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 description clearly states the tool creates a BRC quote using structured MCP fields. It distinguishes from sibling tools like brc_create_quote_gen_ref by specifying when to use that alternative (auto-generated references). The verb 'Creates' is specific and the resource 'BRC quote' is unambiguous.

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 guidance on when to use the tool and when not to. It requires a quote reference when manual/unknown, specifies required fields (saleRepId, saleRepCode, analysisCategoryId, accountCode), warns against default/demo values, and outlines the two-step confirmation process with confirmWrite and confirmCounterpartyExplicit. It explicitly states not to use when settings are unknown without user-provided reference.

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/loldwyer/Red'

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