Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List ATO accounts

list_ato_accounts
Read-only

Retrieve a fund's ATO accounts with balances, statement coverage, and ATO reconciliation status to identify the correct ato_account_id.

Instructions

List the fund's ATO accounts (income tax 551, activity statement 001, superannuation 552) with their balance (positive = owed to the ATO, negative = the ATO owes the fund), how far the imported statement reaches, and whether Alpha's running balance agrees with the ATO's. Use to find an ato_account_id.

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_ato_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real substance beyond that with the sign convention for balance (positive owed to ATO, negative ATO owes fund), statement import coverage, and a reconciliation-agreement flag. These are non-obvious interpretation rules that would otherwise be guessed wrong. It does not cover ordering or empty-list behavior, so not 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.

Conciseness4/5

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

Two sentences, front-loaded with the resource and scoped by the parenthetical account codes, which are load-bearing rather than filler. Slightly dense, but no sentence could be removed 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?

With no output schema, the description takes on the burden of describing the returned fields, and it does so for the key three (balance with sign semantics, statement coverage, reconciliation agreement). Remaining gaps — ordering, empty results, or whether an imported statement is a prerequisite — are minor for a single-fund lookup tool.

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?

There is a single parameter and schema description coverage is 100%, with the schema itself explaining how to discover fund_id (whoami or list_funds). The description adds nothing about fund_id, so the baseline of 3 applies — the schema does all the work here.

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 fund's ATO accounts") and immediately disambiguates the account types with the ATO codes (income tax 551, activity statement 001, superannuation 552). An agent can distinguish this from list_ato_transactions or get_ato_position without opening the schema.

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?

"Use to find an ato_account_id" tells the agent exactly which downstream need this tool serves, which is the main selection signal versus the sibling ATO tools. It stops short of naming explicit alternatives or when-not conditions (e.g. use list_ato_transactions for individual line items), so it is clear context rather than a full routing rule.

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