Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List statement balances

list_statement_balances
Read-only

Lists bank accounts' statement closing balances alongside ledger balances and differences to reveal constant or changing variances and 30 June return cash figures.

Instructions

List each bank account's statement closing-balance snapshots (from posted statements or record_statement_balance), each with the ledger balance that day and the difference (opening_anchor: true marks the statement the day before the opening balance date, compared with opening_balance). constant_difference is set when the ledger is out by the same amount at every statement since a date — check the opening balance. With financial_year, also returns per account the 30 June ledger balance the return uses (eofy.ledger_balance), the latest statement balance on or before 30 June, their difference, and whether the account counts as return cash (ATO accounts don't). A difference that changes between statements means the ledger is missing or has extra lines in between. AUD.

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>"
    },
    "name": "list_statement_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
financial_yearNoFinancial year — the label "2023-24" or its numeric id (from list_financial_years)
bank_account_idNoBank account ID (find via list_bank_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4/5.0
Behavior4/5

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

With only readOnlyHint supplied, the description adds substantial behavioral context: the data source ('posted statements or record_statement_balance'), meaning of opening_anchor and constant_difference, EOFY-specific return cash treatment, and AUD currency. It still omits ordering, pagination, permissions, and empty-result behavior, so it stops short of full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with its purpose, but it is a single dense paragraph with parentheticals, em dashes, and semicolons that make it hard to scan. Most content is relevant, but the structure could be split into clearer sentences for field meanings and EOFY behavior.

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 a three-parameter read-only list tool with no output schema, the description explains the key returned fields and how to interpret differences, including EOFY and return-cash semantics. It leaves some return-shape details unstated, such as ordering, pagination, and behavior when no statements exist, but is otherwise complete for correct invocation.

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 beyond the schema for financial_year, explaining that it returns 30 June ledger balance, latest statement balance on or before 30 June, their difference, and return-cash classification. It implies bank_account_id scopes the listing to one account but does not elaborate on that parameter.

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 opens with a specific verb and resource: 'List each bank account's statement closing-balance snapshots,' and immediately describes the accompanying ledger balance and difference. This distinguishes it from siblings like list_bank_accounts, record_statement_balance, and run_account_reconciliation without requiring schema inspection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through diagnostic guidance such as 'check the opening balance' and the explanation that a changing difference means the ledger is missing or has extra lines. However, it never explicitly states when to use this tool versus alternatives like run_account_reconciliation or list_balance_items, nor does it state when not to use it.

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