Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a year-end pack document as JSON

get_year_end_pack_document
Read-only

Retrieve a year-end SMSF pack document as structured JSON to check figures or build working papers. Member statements require a member ID.

Instructions

Return one year-end pack document as structured JSON (headings, tables, lines and figures) — the same content get_year_end_pack_pdf renders — for checking figures or building your own working papers. Document keys come from list_year_end_pack; member_statement also needs member_id. 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>",
      "document": "<document>"
    },
    "name": "get_year_end_pack_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
documentYesWhich document
member_idNoMember ID, for document member_statement
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.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description must carry the rest; it discloses the return shape (headings, tables, lines, figures) and the currency (AUD), which are the behaviors an agent needs. It says nothing about size limits, document availability, or error behavior when a document isn't generated, which keeps it below a 5.

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?

Two sentences, front-loaded with the action and return format, then use cases, then the required-key constraints. No padding or restatement of the title.

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 supplies the return structure and currency, and covers the conditional member_id dependency, which is enough to call it correctly. It omits any mention of error conditions or document-not-available behavior, a minor gap for a read tool.

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 baseline is 3, but the description adds real value: it names list_year_end_pack as the source of valid document keys and states that member_statement additionally requires member_id, which is a conditional requirement rather than a flat field gloss.

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 ('Return one year-end pack document as structured JSON') plus the returned structure (headings, tables, lines, figures), and explicitly distinguishes itself from the sibling get_year_end_pack_pdf by saying it renders the same content.

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?

Gives clear use cases (checking figures, building your own working papers) which implicitly select JSON over the PDF sibling, and routes the agent to list_year_end_pack for document keys. It stops short of an explicit 'use X when, Y when' rule for the PDF alternative.

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