Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List balance-sheet items

list_balance_items
Read-only

Retrieves trustee-entered balance-sheet lines for a fund and financial year, including other assets, borrowings and liabilities that feed SMSF return items and the statement of financial position.

Instructions

List the trustee-entered balance-sheet lines for a financial year — the figures the investment ledger can't derive: other assets (receivables, non-holding plant), borrowings (LRBAs and other loans) and other liabilities (ATO accounts, GST, creditors, rent bonds). These feed SMSF return items 15b O, 16 V and 16 Y and the statement of financial position. Returns per-side totals alongside the rows. Lines from the ATO position have source "ato_position"; typed lines they replaced are listed with counted: false and superseded_by_id, and are left out of the totals.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fund_id": "<fund_id>",
      "financial_year": "<financial_year>"
    },
    "name": "list_balance_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoFilter liabilities: "borrowings" (16 V) or "other" (16 Y)
sideNoFilter by balance-sheet side
fund_idYesFund ID (discover via whoami or list_funds)
financial_yearYesFinancial year — the label "2023-24" or its numeric id (from list_financial_years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.3/5.0
Behavior4/5

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

Beyond readOnlyHint=true it discloses real behavioural detail: per-side totals come back alongside rows, ATO-sourced rows carry source 'ato_position', and superseded typed rows appear with counted: false and superseded_by_id yet are excluded from totals. That is exactly the kind of subtlety an agent could not infer from annotations; only ordering/pagination is left unstated.

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?

Front-loaded with the core action, then scope, then return-shape caveats. The parenthetical item lists are dense but each maps to a filter value or return item, so they carry weight; the sentence about ATO position and superseded rows is the longest but is the highest-value part.

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?

With no output schema, the description correctly compensates by describing the payload: rows plus per-side totals plus superseded-row markers. For a read-only filtered list of four parameters this is close to complete; the remaining gap is pagination or ordering behaviour, which is not mentioned.

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, and the prose earns the extra point by giving concrete content for the enum values — borrowings means LRBAs and loans, other means ATO accounts, GST, creditors, rent bonds, receivables, non-holding plant. That helps an agent pick the right filter rather than guessing what 'other' means.

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?

Specific verb plus resource plus scope: 'list the trustee-entered balance-sheet lines for a financial year'. It also delimits the resource against neighbours by saying these are 'the figures the investment ledger can't derive', which separates it from list_statement_balances, list_holdings and get_ato_position.

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 clear context for when to reach for it: other assets, borrowings and other liabilities, tied to SMSF return items 15b O, 16 V and 16 Y. It does not state explicit exclusions or name the read alternatives (e.g. get_ato_position), so an agent must infer routing from the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools