Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List the year-end pack

list_year_end_pack
Read-only

Lists a financial year's year-end pack documents, headline totals, supporting evidence index, and net assets reconciliation for SMSF review and return verification.

Instructions

List the documents in a financial year's year-end pack — statement of financial position, operating statement, detailed operating statement (income and market movements by holding), notes to the financial statements, trustees' declaration, investment summary, tax reconciliation, one member statement per member, trustee minutes, trustee representation letter and the return — with headline totals (benefits accrued, income tax expense, net assets, taxable income, whether the tax reconciliation ties to the return) and evidence_index (the year's supporting documents, permanent ones included, each with a file_path) and net_assets_reconciliation: members' opening balances + benefits accrued + rollovers in − benefits paid against net assets at 30 June, with the difference (null without member statements). All figures come from the same services as the return. Amounts in 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>",
      "financial_year": "<financial_year>"
    },
    "name": "list_year_end_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real context beyond that: figures come from the same services as the return, amounts are in AUD, and net_assets_reconciliation's difference is null when member statements are absent. That null-condition is exactly the kind of edge case an agent needs, though pagination/size limits on the document list are not covered.

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

Conciseness2/5

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

It is a single run-on sentence that crams the full document inventory, three result payloads and a reconciliation formula into one breath. The core purpose is front-loaded, but the 13-item document enumeration and the inline arithmetic for net_assets_reconciliation would read far better as structure or be trimmed since the agent can discover documents from the result.

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 carries the full burden of describing returns, and it does so thoroughly — document inventory, headline totals, evidence_index with file_path, and the reconciliation formula. Only the ordering/size of the returned document list is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters already document their discovery paths (whoami/list_funds, list_financial_years). The description adds nothing about the fund_id/financial_year format beyond repeating 'a financial year's year-end pack', so the baseline 3 applies.

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?

States a specific verb and resource ('List the documents in a financial year's year-end pack') and enumerates the exact document set plus the headline totals, evidence_index and net_assets_reconciliation payloads. An agent can distinguish this from get_year_end_pack_document and get_year_end_pack_pdf by the fact that this returns the whole inventory rather than one document.

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 only implied by the verb 'List' — the description never says when to reach for this versus get_year_end_pack_document (single document) or get_year_end_pack_pdf, nor whether the pack must be generated first. The agent must infer the routing from the name alone.

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