Skip to main content
Glama
steamau

Beeswax Shares MCP Server

by steamau

Record trade

record_trade

Record a buy or sell trade directly to your SMSF ledger with immediate write and no review step. Use idempotency keys to avoid duplicates.

Instructions

Record a buy or sell directly to your SMSF ledger. This writes immediately — there is no review step. Use whenever a trade is found in an email, contract note or conversation. Identify the holding by ticker or holding_id; the holding must already exist (use create_holding first if it doesn't). Always pass external_ref when the source has a stable ID (e.g. email message id + ticker + date) — it is an idempotency key, so re-running the same import will not create duplicates. Pass reasoning to record why (it is saved on the ledger entry for the audit trail). Amounts in 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")
quantityNoUnits bought/sold
reasoningNoWhy this trade is recorded (cite the source) — saved to the audit trail
broker_feeNoBrokerage fee
holding_idNoHolding ID, if already known
external_refNoIdempotency key derived from the source, e.g. '<email-message-id>:VAS:2026-05-30'
total_amountYesTotal consideration (AUD unless currency set)
price_per_unitNoPrice per unit
transaction_dateYesTrade date as an ISO date, e.g. "2026-05-30"
transaction_typeYesTrade direction
Behavior5/5

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

The description discloses the tool writes immediately with no review step, aligning with annotations (readOnlyHint=false, destructiveHint=false). It also explains idempotency via external_ref, currency default (AUD), and audit trail for reasoning. No contradictions with annotations.

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 well-structured with clear instructions in separate sentences. Each sentence adds value, though it could be slightly more concise without losing meaning.

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?

The description covers all necessary aspects for a trade recording tool: when to use, prerequisites, parameters, behavioral traits. However, it does not explicitly mention the return value/output, which is a minor gap given no output schema.

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 high (92%), and the description adds meaningful context beyond the schema: identifying holding by ticker or holding_id, mandatory external_ref when source has stable ID, reasoning for audit trail, and currency default (AUD). This adds value for parameter 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?

The description clearly states the tool records a buy or sell trade to the SMSF ledger, with specific verb ('Record') and resource ('trade'). It distinguishes from sibling tools like record_cash_transaction, record_cost, record_income, which cover different financial events.

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 explicitly states when to use (trade found in email/contract note/conversation) and when to use a precursor (use create_holding first if holding doesn't exist). It also provides guidance on passing external_ref for idempotency and 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