Skip to main content
Glama

Red by Big Red Cloud

by io.github.BigRedCloud

Batch Cash Receipts

brc_batch_cash_receipts
Destructive

Processes a batch of BRC cash receipts. Maximum 20 items per batch request. 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
NameRequiredDescriptionDefault
itemsYesBatch items to process. Maximum 20 items per request.
routeTokenYesOpaque routeToken from brc_route_request for this action workflow. Required for transactional tools. Routing permission only — does not replace preview-before-posting or confirmWrite.
companyNameYesCompany context name, for example YOUR-COMPANY-NAME.
confirmWriteNoMust 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.
connectionRefNoOpaque 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.
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 preview, was inferred from context, or was filled in without the user's explicit choice in this conversation.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • removedInput schema / properties / confirmCrAnalysisCategory
      Removed value: -{
-  "description": "Applies to every sales document item in this batch. Set true only after the user confirms a CR (customer) sales analysis account code is intentional for these product lines.",
-  "type": "boolean"
-}
    • changedInput schema / properties / items / items / additionalProperties
      Previous value: -{}New value: +false
    • addedInput schema / properties / items / items / properties
      Added value: +{
+  "item": {
+    "oneOf": [
+      {
+        "additionalProperties": false,
+        "properties": {
+          "acEntries": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "accountCode": {
+                  "description": "Cash Receipts analysis account code.",
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "analysisCategoryId": {
+                  "description": "Cash Receipts analysis category id.",
+                  "exclusiveMinimum": 0,
+                  "maximum": 9007199254740991,
+                  "type": "integer"
+                },
+                "description": {
+                  "description": "Analysis-line description.",
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "id": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "value": {
+                  "description": "Positive portion of the receipt total assigned to this analysis entry.",
+                  "exclusiveMinimum": 0,
+                  "type": "number"
+                }
+              },
+              "required": [
+                "accountCode",
+                "analysisCategoryId",
+                "description",
+                "value"
+              ],
+              "type": "object"
+            },
+            "minItems": 1,
+            "type": "array"
+          },
+          "bookTranTypeId": {
+            "const": 1,
+            "description": "Cash Receipt book transaction type id. Must be 1.",
+            "type": "number"
+          },
+          "discount": {
+            "type": "number"
+          },
+          "entryDate": {
+            "description": "Entry date in ISO format.",
+            "minLength": 1,
+            "type": "string"
+          },
+          "note": {
+            "description": "Cash Receipt note.",
+            "minLength": 1,
+            "type": "string"
+          },
+          "procDate": {
+            "description": "Processing date in ISO format.",
+            "minLength": 1,
+            "type": "string"
+          },
+          "reference": {
+            "type": "string"
+          },
+          "total": {
+            "description": "Positive Cash Receipt total.",
+            "exclusiveMinimum": 0,
+            "type": "number"
+          },
+          "vatEntries": {
+            "description": "Optional manual VAT split. Removed before transmission when Enable VAT on Cash Receipts is disabled.",
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "amount": {
+                  "description": "Positive portion of the receipt total assigned to this VAT rate; this is not the VAT amount.",
+                  "exclusiveMinimum": 0,
+                  "type": "number"
+                },
+                "id": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "percentage": {
+                  "description": "VAT percentage.",
+                  "type": "number"
+                },
+                "vatRateId": {
+                  "description": "BRC VAT rate id.",
+                  "exclusiveMinimum": 0,
+                  "maximum": 9007199254740991,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "vatRateId",
+                "percentage",
+                "amount"
+              ],
+              "type": "object"
+            },
+            "minItems": 1,
+            "type": "array"
+          }
+        },
+        "required": [
+          "total",
+          "note",
+          "entryDate",
+          "procDate",
+          "bookTranTypeId",
+          "acEntries"
+        ],
+        "type": "object"
+      },
+      {
+        "oneOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "accountCode": {
+                "description": "Cash Receipts analysis account code.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "analysisCategoryId": {
+                "description": "Cash Receipts analysis category id.",
+                "exclusiveMinimum": 0,
+                "maximum": 9007199254740991,
+                "type": "integer"
+              },
+              "bookTranTypeId": {
+                "const": 1,
+                "description": "Cash Receipt book transaction type id. Must be 1.",
+                "type": "number"
+              },
+              "description": {
+                "description": "Analysis-line description.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "discount": {
+                "type": "number"
+              },
+              "entryDate": {
+                "description": "Entry date in ISO format.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "note": {
+                "description": "Cash Receipt note.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "procDate": {
+                "description": "Processing date in ISO format.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "reference": {
+                "type": "string"
+              },
+              "total": {
+                "description": "Positive Cash Receipt total.",
+                "exclusiveMinimum": 0,
+                "type": "number"
+              }
+            },
+            "required": [
+              "total",
+              "note",
+              "entryDate",
+              "procDate",
+              "bookTranTypeId",
+              "analysisCategoryId",
+              "accountCode",
+              "description"
+            ],
+            "type": "object"
+          },
+          {
+            "additionalProperties": false,
+            "properties": {
+              "accountCode": {
+                "description": "Cash Receipts analysis account code.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "analysisCategoryId": {
+                "description": "Cash Receipts analysis category id.",
+                "exclusiveMinimum": 0,
+                "maximum": 9007199254740991,
+                "type": "integer"
+              },
+              "bookTranTypeId": {
+                "const": 1,
+                "description": "Cash Receipt book transaction type id. Must be 1.",
+                "type": "number"
+              },
+              "description": {
+                "description": "Analysis-line description.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "discount": {
+                "type": "number"
+              },
+              "entryDate": {
+                "description": "Entry date in ISO format.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "note": {
+                "description": "Cash Receipt note.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "procDate": {
+                "description": "Processing date in ISO format.",
+                "minLength": 1,
+                "type": "string"
+              },
+              "reference": {
+                "type": "string"
+              },
+              "total": {
+                "description": "Positive Cash Receipt total.",
+                "exclusiveMinimum": 0,
+                "type": "number"
+              },
+              "vatPercentage": {
+                "description": "VAT percentage. Must be supplied with vatRateId.",
+                "type": "number"
+              },
+              "vatRateId": {
+                "description": "BRC VAT rate id.",
+                "exclusiveMinimum": 0,
+                "maximum": 9007199254740991,
+                "type": "integer"
+              }
+            },
+            "required": [
+              "total",
+              "note",
+              "entryDate",
+              "procDate",
+              "bookTranTypeId",
+              "analysisCategoryId",
+              "accountCode",
+              "description",
+              "vatRateId",
+              "vatPercentage"
+            ],
+            "type": "object"
+          }
+        ]
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "acCode": {
+            "description": "Customer account code.",
+            "minLength": 1,
+            "type": "string"
+          },
+          "bookTranTypeId": {
+            "const": 1,
+            "description": "Cash Receipt book transaction type id. Must be 1.",
+            "type": "number"
+          },
+          "customerId": {
+            "description": "BRC customer id.",
+            "exclusiveMinimum": 0,
+            "maximum": 9007199254740991,
+            "type": "integer"
+          },
+          "discount": {
+            "type": "number"
+          },
+          "entryDate": {
+            "description": "Entry date in ISO format.",
+            "minLength": 1,
+            "type": "string"
+          },
+          "ledger": {
+            "description": "Customer-ledger amount; must equal total.",
+            "exclusiveMinimum": 0,
+            "type": "number"
+          },
+          "note": {
+            "description": "Cash Receipt note.",
+            "minLength": 1,
+            "type": "string"
+          },
+          "procDate": {
+            "description": "Processing date in ISO format.",
+            "minLength": 1,
+            "type": "string"
+          },
+          "reference": {
+            "type": "string"
+          },
+          "total": {
+            "description": "Positive Cash Receipt total.",
+            "exclusiveMinimum": 0,
+            "type": "number"
+          }
+        },
+        "required": [
+          "total",
+          "note",
+          "entryDate",
+          "procDate",
+          "bookTranTypeId",
+          "customerId",
+          "acCode",
+          "ledger"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  "opCode": {
+    "const": 1,
+    "description": "BRC batch create operation code. Must be 1.",
+    "type": "number"
+  }
+}
    • removedInput schema / properties / items / items / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / items / items / required
      Added value: +[
+  "opCode",
+  "item"
+]
    • removedInput schema / properties / priceBasis
      Removed value: -{
-  "description": "Applies to every sales invoice/credit note item in this batch. Required when Gross Price Entry is enabled. Use `gross` when unit prices are VAT-inclusive/gross. Use `net` when unit prices are VAT-exclusive/net.",
-  "enum": [
-    "net",
-    "gross"
-  ],
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • addedInput schema / properties / routeToken
      Added value: +{
+  "description": "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.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "companyName",
-  "items"
-]New value: +[
+  "companyName",
+  "items",
+  "routeToken"
+]
  3. Changed2 schema fields changed
    • removedInput schema / properties / routeToken
      Removed value: -{
-  "description": "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.",
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "companyName",
-  "items",
-  "routeToken"
-]New value: +[
+  "companyName",
+  "items"
+]
  4. Changed2 schema fields changed
    • addedInput schema / properties / routeToken
      Added value: +{
+  "description": "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.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "companyName",
-  "items"
-]New value: +[
+  "companyName",
+  "items",
+  "routeToken"
+]
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true and readOnlyHint=false, so the write nature is known. The description adds real behavioral detail: the first call without confirmWrite returns confirmation_required and a payload preview, confirmWrite applies the previewed change only after explicit confirmation, and confirmation is scoped to the counterparty in the current preview. This two-phase flow is not inferable from annotations and is critical for safe invocation.

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?

Every sentence earns its place: batch limit, token validity, placeholder invalidity, no-bypass behavior, confirmation response, confirmWrite semantics, and counterparty scoping. The structure is front-loaded with the most important constraints, and the sentence-per-line layout makes the dense information reasonably scannable. Some grouping into bullets would improve scanability, but there is no bloat.

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?

Even without an output schema, the description tells an agent what to expect on the first call (confirmation_required and payload preview) and what confirmWrite: true does. Combined with a rich schema covering connectionRef, items constraints, and date formats, the core execution flow and prerequisites are adequately disclosed. It doesn't detail the exact preview payload shape or error conditions, but the essential transactional behavior is well covered.

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

Parameters3/5

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

Schea description coverage is 100%, so the baseline is 3. The description does add interpretive context for routeToken, confirmWrite, and confirmCounterpartyExplicit, particularly the token's permission-only nature and the confirmation scoping. However, most of these meanings already exist in the schema parameter descriptions, so the marginal value added by the description is moderate rather than substantial.

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 opens with 'Processes a batch of BRC cash receipts,' which is a specific verb plus resource and clearly indicates this is a batch operation. The resource name and 'cash receipts' phrasing distinguish it from batch cash payments or other BRC batch tools, though it doesn't explicitly name a 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 Guidelines4/5

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

The description provides concrete operational guidance: maximum 20 items per request, valid routeToken required, placeholder tokens invalid, and confirmation flags must only be true after explicit user confirmation. It clearly states when confirmWrite and confirmCounterpartyExplicit should be set, and that preflight alone is not confirmation. It doesn't explicitly discuss when to use the batch form versus a single-create sibling, but the usage constraints are concrete and actionable.

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 toolsInspect
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.

Resources