Skip to main content
Glama

Red by Big Red Cloud

by io.github.BigRedCloud

Batch Customers

brc_batch_customers
Destructive

Processes a batch of customers using explicit identity, VAT classification, and optional contact fields. 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.

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.

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": {
+    "additionalProperties": false,
+    "properties": {
+      "additionalEmails": {
+        "description": "Optional additional email addresses.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "address": {
+        "description": "Optional address lines.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "businessIdentifierCode": {
+        "description": "Optional BIC. Blank values are accepted and omitted by the existing builder.",
+        "type": "string"
+      },
+      "code": {
+        "description": "BRC account code, maximum eight characters.",
+        "maxLength": 8,
+        "minLength": 1,
+        "type": "string"
+      },
+      "contact": {
+        "description": "Optional contact name. Blank values are accepted and omitted by the existing builder.",
+        "type": "string"
+      },
+      "creditTerms": {
+        "description": "Optional credit terms in days.",
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "email": {
+        "description": "Optional email address. Blank values are accepted and omitted by the existing builder.",
+        "type": "string"
+      },
+      "fax": {
+        "description": "Optional fax number. Blank values are accepted and omitted by the existing builder.",
+        "type": "string"
+      },
+      "internationalBankAccountNumber": {
+        "description": "Optional IBAN. Blank values are accepted and omitted by the existing builder.",
+        "type": "string"
+      },
+      "mobile": {
+        "description": "Optional mobile number. Blank values are accepted and omitted by the existing builder.",
+        "type": "string"
+      },
+      "name": {
+        "description": "Customer or supplier name.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "phone": {
+        "description": "Optional phone number. Blank values are accepted and omitted by the existing builder.",
+        "type": "string"
+      },
+      "vatAnalysisTypeId": {
+        "description": "BRC VAT analysis type id.",
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "vatReg": {
+        "description": "Optional VAT registration number. Blank values are accepted and omitted by the existing builder.",
+        "type": "string"
+      },
+      "vatRegistered": {
+        "description": "Whether the owner is VAT registered.",
+        "type": "boolean"
+      },
+      "vatType": {
+        "description": "BRC VAT type integer. Resolve the intended value from the connected company's VAT reference data.",
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "code",
+      "name",
+      "vatType",
+      "vatAnalysisTypeId"
+    ],
+    "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

A4.3/5.0
Behavior5/5

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

Annotations already mark this as a write and destructive, and the description adds substantial behavior beyond that: token validity lifecycle, placeholder token invalidity, preflight returning confirmation_required with a payload preview, confirmWrite:true applying the previewed change only after explicit confirmation, and the warning that passing preflight is not confirmation. This is exactly the kind of high-risk behavioral context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but efficient: it front-loads purpose and batch size, then covers token validity, preview requirement, and explicit confirmation semantics in five tight sentences. Every sentence carries a constraint or behavior necessary for safe invocation, with no filler.

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 a complex transactional tool with nested items and no output schema, the description covers the critical workflow: token requirements, preview behavior, confirmWrite semantics, and max batch size. The schema supplies complete parameter documentation. It does not describe success/error response shapes in natural language, but the preview/confirmation flow is adequately disclosed.

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 coverage is 100%, so the baseline is 3. The description adds meaningful parameter-level context beyond the schema, especially for routeToken (valid through lookup, preview, and permitted transaction; placeholder tokens invalid) and confirmWrite (preflight behavior and the distinction between preview and confirmation). This goes beyond the schema's own descriptions.

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 states a specific action ('Processes') and resource ('a batch of customers') and adds scope ('Maximum 20 items per batch request'). It is clear enough to distinguish from non-customer batch tools, though 'Processes' is less precise than 'Creates' — the create semantics are only fully visible through the schema's opCode const 1.

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 gives concrete invocation context: a valid routeToken from the matching workflow is required, placeholder tokens are invalid, and the preview/confirmWrite contract is spelled out. It does not explicitly state when to prefer this over single-entity siblings like brc_create_customer, but the batch-specific context is clear 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