Red by Big Red Cloud

Create Accrual

brc_create_accrual

Destructive

Creates an accrual after returning an unconfirmed payload preview. 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

Name	Required	Description
`total`	Yes	Accrual total amount.
`acCode`	Yes	Nominal account code, for example 4000.
`procDate`	Yes	Processing date, for example 2024-03-15T00:00:00.
`entryDate`	Yes	Entry date, for example 2024-03-01T00:00:00.
`reference`	Yes	Accrual reference, for example ACC0001.
`routeToken`	Yes	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.
`companyName`	Yes	Company context name, for example YOUR-COMPANY-NAME.
`firstDetail`	No	First detail text.
`confirmWrite`	No	Must be true only after the user explicitly confirms creating this accrual.
`secondDetail`	No	Second detail text.
`connectionRef`	No	Opaque 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.

Changed2 schema fields changedAug 5, 2026

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",
-  "acCode",
-  "entryDate",
-  "procDate",
-  "reference",
-  "total"
-]New value: +[
+  "companyName",
+  "acCode",
+  "entryDate",
+  "procDate",
+  "reference",
+  "total",
+  "routeToken"
+]

Changed2 schema fields changedAug 4, 2026

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",
-  "acCode",
-  "entryDate",
-  "procDate",
-  "reference",
-  "total",
-  "routeToken"
-]New value: +[
+  "companyName",
+  "acCode",
+  "entryDate",
+  "procDate",
+  "reference",
+  "total"
+]

Changed2 schema fields changedAug 4, 2026

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",
-  "acCode",
-  "entryDate",
-  "procDate",
-  "reference",
-  "total"
-]New value: +[
+  "companyName",
+  "acCode",
+  "entryDate",
+  "procDate",
+  "reference",
+  "total",
+  "routeToken"
+]

First observedJul 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only provide destructiveHint: true. The description goes well beyond that by disclosing the confirmation workflow: calls without confirmWrite return confirmation_required and a payload preview, confirmWrite applies the previewed change, placeholder tokens are invalid, and routeToken does not bypass preview or confirmation requirements.

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 dense and front-loaded with the core action. Every sentence contributes something useful, though there is slight redundancy between 'returns an unconfirmed payload preview' and the later explanation of the preview/confirm flow.

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?

For an 11-parameter creation tool with no output schema, it explains the essential confirmation protocol, routeToken lifecycle, and the meaning of confirmWrite. A minor gap is that it does not describe what the final successful response after confirmWrite: true looks like.

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 semantics for confirmWrite and routeToken beyond the schema: no-confirm returns a preview, confirmWrite applies the previewed change, and the token remains valid through lookup/preview/transaction. This gives the agent concrete decision guidance for those parameters.

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 states a specific verb and resource ('Creates an accrual') and immediately adds the distinguishing two-phase preview-then-confirm behavior. This clearly separates it from the update/get/delete accrual siblings even without comparing them explicitly.

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?

It gives strong operational guidance: a routeToken is required, confirmWrite: true must only follow explicit user confirmation, and preflight does not count as confirmation. It does not explicitly name sibling alternatives or state when not to use this tool, so it stops short of a 5.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Create Accrual

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources