Skip to main content
Glama
BigRedCloud

Red MCP Server

Official
by BigRedCloud

brc_create_purchase

Creates a purchase in Big Red Cloud using structured fields. Requires explicit user confirmation of a draft preview and counterparty before posting.

Instructions

Creates a BRC purchase using structured MCP fields. Requires a reference when the company is configured for manual purchase references; otherwise prefer brc_create_purchase_gen_ref. 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
noteYesPurchase note.
acCodeYesSupplier account code, for example SUP001.
procDateYesProcessing date in ISO format.
entryDateYesEntry date in ISO format.
netAmountYesNet amount before VAT.
referenceNoRequired when the company is configured for manual purchase references.
vatRateIdYesVAT rate id.
supplierIdYesSupplier id, for example 26180406.
accountCodeYesNominal/account code.
companyNameYesCompany context name, for example YOUR-COMPANY-NAME.
descriptionYesAnalysis line description.
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.
vatPercentageYesVAT percentage.
bookTranTypeIdYesPurchase book transaction type id.
analysisCategoryIdYesPurchases analysis category id.
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.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explains the two-phase commit behavior (preview then confirmation), clarifies that passing preflight is not confirmation, and requires explicit counterparty confirmation. It does not explicitly state the side effects (e.g., database creation), but the workflow details are sufficiently transparent. Could be slightly more explicit about success outputs.

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 appropriately sized for a complex tool with multi-step workflow. It front-loads the main purpose and key conditions, then structures the workflow. Every sentence serves a purpose, though it could be slightly more concise by combining some conditional statements.

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 16 parameters (13 required) and no output schema, the description covers the essential workflow, confirmation steps, and counterparty confirmation. It does not explain return values or error handling, but for a creation tool with two-phase commit, the guidance is sufficiently complete 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 covers 100% of parameters with descriptions, but the description adds significant context for confirmWrite and confirmCounterpartyExplicit, explaining their workflow semantics. It also clarifies when reference is required. For other parameters like netAmount, schema descriptions suffice, but the tool's description adds value for the nuanced boolean params.

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 starts with 'Creates a BRC purchase using structured MCP fields', clearly stating the verb and resource. It also distinguishes from sibling tool brc_create_purchase_gen_ref by specifying when each should be used (manual reference vs auto-generated), ensuring differentiation.

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?

Explicitly states when to use this tool (company configured for manual reference) and when to prefer brc_create_purchase_gen_ref. Provides a detailed multi-step workflow: first call without confirmWrite, then retry with confirmWrite only after explicit user confirmation. Also requires confirmCounterpartyExplicit after the user explicitly names or confirms the counterparty. This is clear and actionable guidance.

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