Skip to main content
Glama
BigRedCloud

Red MCP Server

Official
by BigRedCloud

brc_create_bank_account

Create a Big Red Cloud bank account using account code, details, last cheque number, and existing nominal account. User must explicitly confirm creation.

Instructions

Creates a BRC bank account. Do not call this tool with confirmCreate=true until the user has reviewed a plain-English summary and explicitly confirmed creation. Required fields: acCode, details, lastChq, and nominalAcCode. categoryId is optional; BRC may create the Bank Payments category automatically when categoryId is omitted. nominalAcCode must reference an existing balance-sheet bank nominal account created in BRC setup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
acCodeNoBank account code, for example 1603.
addressNo
balanceNoOpening/current starting balance.
detailsNoBank account description/name.
lastChqNoLast cheque number, for example 000001.
payloadNoOptional raw bank account payload.
sortCodeNo
categoryIdNoBank Payments category type id from brc_list_category_types.
accountNameNo
companyNameYesCompany context name, for example YOUR-COMPANY-NAME.
accountNumberNo
confirmCreateNoMust be true only after the user explicitly confirms creation.
isDefaultBankNo
nominalAcCodeNoExisting linked nominal account code. This must already exist in Big Red Cloud and will be sent to the API as account.acCode.
creditorSchemeNo
bankFeedsSourceNo
businessIdentifierCodeNo
internationalBankAccountNumberNo
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses automatic category creation when categoryId omitted, and requirement for nominalAcCode to exist. Does not cover authentication or response.

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?

Single paragraph of 4 sentences, concise and to the point. Could be slightly more structured (e.g., bullet points for required fields).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 18 parameters and no output schema, description covers core workflow and key constraints but lacks details on many parameters and return behavior. Sufficient for basic use but not fully comprehensive.

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?

Schema coverage 50%. Description highlights required fields (acCode, details, lastChq, nominalAcCode) and explains categoryId optionality, but many parameters (address, balance, sortCode, etc.) remain unexplained.

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 'Creates a BRC bank account', which is a specific verb+resource. Sibling tools are distinct create operations for other entities, so no confusion.

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?

Explicitly warns against calling with confirmCreate=true before user confirmation, and lists required fields. However, no mention of when not to use or alternatives.

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