Skip to main content
Glama
steamau

Beeswax Shares MCP Server

by steamau

Record income

record_income

Record dividend, distribution, interest, or rental income directly to your SMSF ledger without review. Use when a dividend statement, distribution advice, or rent receipt is found.

Instructions

Record an income event — dividend, distribution, interest or rental income — directly to your SMSF ledger. This writes immediately; there is no review step. Use when a dividend statement, distribution advice or rent receipt is found. Identify the holding by ticker or holding_id (it must already exist). Include franking_credits for franked dividends (important for SMSF tax). Always pass external_ref when the source has a stable ID so repeat imports are idempotent. Pass reasoning to record why (saved for the audit trail). All amounts AUD unless currency says otherwise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
tickerNoTicker symbol of the holding (preferred way to identify it)
fund_idYesFund ID (discover via whoami or list_funds)
currencyNoCurrency code (default "AUD")
reasoningNoWhy this income is recorded (cite the source) — saved to the audit trail
holding_idNoHolding ID, if already known
external_refNoIdempotency key derived from the source, e.g. '<email-message-id>:VAS:2026-03-28'
payment_dateNoPayment date as an ISO date, e.g. "2026-05-30"
total_amountYesCash amount received (AUD unless currency set)
ex_dividend_dateNoEx-dividend date as an ISO date, e.g. "2026-05-30"
franking_creditsNoFranking credits attached (AUD) — for franked dividends
transaction_dateYesIncome date (usually the payment date) as an ISO date, e.g. "2026-05-30"
transaction_typeYesIncome type
Behavior5/5

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

Describes that the tool writes immediately with no review step, and mentions idempotency behavior via external_ref. This adds value beyond annotations (readOnlyHint=false, destructiveHint=false). No contradictions.

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?

Five sentences, front-loaded with core purpose. Every sentence adds distinct value. No fluff or redundancy.

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

Completeness5/5

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

Given high schema coverage and no output schema, the description covers use cases, parameter guidance, and behavioral aspects comprehensively. All required context for an agent to use the tool correctly is present.

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 92%, so baseline is 3. Description adds meaning for ticker vs holding_id, franking credits importance, external_ref purpose, reasoning for audit trail, and default currency. Provides good supplemental context.

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?

Description clearly states it records income events (dividend, distribution, interest, rental income) to an SMSF ledger, distinguishing it from sibling tools like record_cost or record_trade. It specifies the resource and action.

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 states when to use: for dividend statements, distribution advice, or rent receipts. Provides guidance on identifying holdings, including franking credits, using external_ref for idempotency, and adding reasoning for audit trail.

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