Skip to main content
Glama
steamau

Beeswax Shares MCP Server

by steamau

Record cash transaction

record_cash_transaction

Enter a signed cash transaction onto a bank account for SMSF funds without live feeds. Supports categories like contributions, fees, interest, and transfers with idempotency key.

Instructions

Record a cash movement directly on a bank account — a contribution, fee, interest, pension/benefit payment, transfer or tax payment — for accounts with no live bank feed, or one-off entries. Writes directly to the cash ledger (low-risk record-keeping, like record_cost; feed-sourced rows arrive automatically instead). Amount is SIGNED: positive = money in (credit), negative = money out (debit), AUD. Contributions and benefit payments require fund_member_id. Pass external_ref as an idempotency key so re-running an import won't duplicate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesSigned amount in AUD: positive = money in, negative = money out
fund_idYesFund ID (discover via whoami or list_funds)
categoryYesSMSF category, e.g. "income_bank_interest", "expense_bank_fee", "contribution_concessional", "pension_payment", "tax_income_payment", "internal_transfer" (default "uncategorised")
referenceNoBank/statement reference
descriptionNoNarration
posted_dateYesDate the transaction posted as an ISO date, e.g. "2026-05-30"
external_refNoStable source ID for idempotency (e.g. statement line id)
tax_componentNoFor tax rows: "payg", "income_tax", "refund", "franking_refund", "division_296"
fund_member_idNoMember the contribution/benefit belongs to (required for contribution_* and pension/benefit)
tax_deductibleNo
bank_account_idYesBank account the movement belongs to (find via list_bank_accounts)
contribution_typeNoFor contributions: "concessional", "non_concessional", "employer_sg", "spouse", "government_cocontribution"
Behavior4/5

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

Describes write behavior to cash ledger as low-risk record-keeping, mentions idempotency via external_ref. Annotations already note it's not read-only or destructive, so added context about idempotency and ledger impact is valuable.

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 covers all key aspects without fluff. Could be slightly more structured but remains efficient and focused.

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 12 parameters and no output schema, description addresses usage context, parameter semantics, and behavioral notes. Idempotency and category-specific requirements are well covered. Missing output description is acceptable given schema coverage.

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?

With 92% schema coverage, description adds meaning beyond schema: amount is signed, external_ref as idempotency key, fund_member_id required for certain categories. This aids correct usage.

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?

Clearly states it records cash movements on a bank account, listing specific categories and distinguishing from feed-sourced rows. Sibling tools like record_cost are referenced, showing differentiation.

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?

Explicitly says when to use: accounts with no live bank feed or one-off entries. Contrasts with automatic feed-sourced rows and mentions similar tool record_cost. Also notes required context for contributions/benefits.

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/steamau/beeswax-desktop'

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