Skip to main content
Glama
BigRedCloud

Red MCP Server

Official
by BigRedCloud

brc_create_cash_payment

Records a cash payment in Big Red Cloud: pay suppliers, lodge to bank, or allocate to analysis categories. Requires explicit user confirmation before posting.

Instructions

Creates a BRC cash payment. Use supplierId + ledger for supplier payments, bankAccountId + lodgement for bank lodgements, or analysisCategoryId + accountCode for analysed expenses. Analysis categories must be from the Cash Payments book (CP01-CP03) and accountCode must match the category. 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
noteYes
totalYes
acCodeNoSupplier account code for ledger payments.
ledgerNoLedger amount; must equal total for supplier payments.
discountNo
procDateNoProcessing date in ISO format. Defaults to entryDate.
entryDateNoEntry date in ISO format. Defaults to today.
lodgementNoLodgement amount; must equal total when lodging to bank.
supplierIdNoSupplier id for ledger payments.
accountCodeNoAnalysis account code matching analysisCategoryId, for example CP01.
companyNameYesCompany context name, for example YOUR-COMPANY-NAME.
descriptionNoAnalysis 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.
bankAccountIdNoBank account id for lodgements.
bookTranTypeIdNoCash Payment book transaction type id.
bankAccountCodeNoBank account code for lodgements.
analysisCategoryIdNoCash Payments analysis category id (categoryTypeId 1391170).
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?

With no annotations provided, the description carries the full burden. It explains the two-phase confirmation flow, constraints on analysis categories, and counterparty confirmation needs. However, it does not describe the final success response or potential errors, which is a gap for a creation 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 relatively long but every sentence serves a purpose. It is front-loaded with the core purpose and usage patterns. Minor redundancy (e.g., 'Passing preflight is not confirmation' could be integrated) but overall well-structured.

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 the tool's complexity (18 parameters, three payment types, two-step confirmation), the description covers the essential workflow and constraints well. It lacks output schema details but mentions the preview response. Overall fairly complete for the complexity.

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

Parameters5/5

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

The description adds significant meaning beyond the input schema by explaining which parameter combinations to use for each payment type, the requirement that analysis categories be from CP01-CP03, and the semantics of confirmWrite and confirmCounterpartyExplicit. This is valuable given the tool's complexity.

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 it creates a BRC cash payment and distinguishes among three usage patterns (supplier payment, bank lodgement, analysed expenses). This differentiates it from sibling create tools like brc_create_cash_receipt and brc_create_sales_invoice.

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 explicit guidance on when to use each parameter combination (supplierId+ledger, bankAccountId+lodgement, analysisCategoryId+accountCode). It also details the two-step confirmation workflow and counterparty confirmation requirement, giving clear direction on how to invoke the tool correctly and safely.

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