Skip to main content
Glama
loldwyer

Red MCP Server

by loldwyer

brc_create_payment

Create a BRC payment from the Payments book, for supplier payments or analysed bank payments. Requires explicit user confirmation before posting.

Instructions

Creates a BRC payment from the Payments book. Use supplierId for supplier payments, or analysisCategoryId + accountCode for analysed bank payments. Analysis categories must be from the bank's Payments book (BP01-BP06) 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 supplier payments.
discountNo
procDateNoProcessing date in ISO format. Defaults to entryDate.
entryDateNoEntry date in ISO format. Defaults to today.
referenceNo
supplierIdNoSupplier id for supplier payments.
accountCodeNoAnalysis account code matching analysisCategoryId, for example BP01.
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.
bankAccountIdYes
bookTranTypeIdNoCheques Entry / Payments book transaction type id.
bankAccountCodeYes
analysisCategoryIdNoPayments book analysis category id for the selected bank.
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 full burden. It discloses the required two-step workflow (first call returns preview, second call with confirmWrite submits), the need for explicit counterparty confirmation, and the fact that preflight is not confirmation. However, it does not specify the return format of a successful final call, which would be useful.

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 a single dense paragraph that efficiently conveys key information. It is front-loaded with the main purpose, then elaborates on usage paths and workflow. While effective, slight restructuring (e.g., bullet points for different payment types) could improve scanability, but the current form is far from wasteful.

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 has 17 parameters, 5 required, no output schema, and many siblings, the description covers the core workflow: two payment modes, confirmation steps, and counterparty handling. It lacks explicit mention of the final success response or error scenarios, but the provided guidance is sufficient for an agent to execute the correct call sequence.

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. It clarifies the relationship between supplierId and the alternative analysisCategoryId+accountCode combination, and imposes constraints (analysisCategoryId must be from BP01-BP06, accountCode must match category) that are not fully captured in the schema. It also explains the confirmWrite and confirmCounterpartyExplicit semantics in plain language, complementing the schema descriptions.

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 explicitly states 'Creates a BRC payment from the Payments book,' providing a specific verb and resource. It further distinguishes two payment types (supplier and analysed bank), which helps differentiate from sibling tools like brc_create_cash_payment or brc_create_purchase.

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 gives clear when-to-use guidance: 'use supplierId for supplier payments, or analysisCategoryId + accountCode for analysed bank payments.' It also explains the two-call confirmation process and the condition for confirmCounterpartyExplicit, with explicit 'do not' instructions, making usage rules unambiguous.

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/loldwyer/Red'

If you have feedback or need assistance with the MCP directory API, please join our Discord server