Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create ATO account

create_ato_account

Adds a fund's income tax, activity statement, or superannuation account in the Tax Office records, rejects duplicate account types, and prepares it for statement import.

Instructions

Add one of the fund's accounts with the Tax Office: income_tax (551), activity_statement (001, the Integrated Client Account — a fund registered for GST or paying PAYG instalments has one) or superannuation (552). A fund has at most one of each; asking for a type it already has is refused. Alpha also adds the activity statement account by itself when the fund is GST-registered or pays PAYG instalments, so check list_ato_accounts first. Import its statement afterwards with import_ato_statement.

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

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
reasoningNoWhy you are making this change — recorded on the audit log entry for this write
account_typeYesWhich ATO account
display_nameNoDefaults to e.g. "Activity statement (001)"
external_refNoYour stable ID for this write (e.g. a statement line or document reference). Repeating a call with the same external_ref replays the first result instead of writing twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive write, so the description adds genuinely new behavioral facts: a fund has at most one account of each type, requesting an existing type is refused, and Alpha may have already created the activity statement account. It does not mention permission/role requirements or what the response body looks like, so it falls short of 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?

Front-loaded with the action, then types, then constraints, then the sibling hand-off — a logical progression with no filler sentences. It is a single dense paragraph with heavy parenthetical nesting, which slightly hurts scannability but not content value.

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 5-parameter mutation with no output schema, the description covers the domain model (one-per-type), the failure mode (refusal), the external actor (Alpha auto-creation), and the workflow successor (import_ato_statement). Missing only error-recovery detail and any note on what the tool returns on success.

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 would be 3, but the description meaningfully enriches account_type beyond the schema's bare "Which ATO account" by explaining what activity_statement means (the Integrated Client Account, required for GST registration or PAYG instalments). It adds no semantics for fund_id, display_name, external_ref, or reasoning, which the schema already documents well.

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?

Opens with a specific verb+resource ("Add one of the fund's accounts with the Tax Office") and enumerates the three creatable account types with their ATO codes (income_tax 551, activity_statement 001, superannuation 552). This clearly separates it from the read-only sibling list_ato_accounts and the follow-up sibling import_ato_statement.

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

Usage Guidelines5/5

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

Gives explicit ordering guidance ("check list_ato_accounts first"), explains the Alpha auto-creation caveat that would otherwise cause a wasted or refused call, and names the natural next step ("Import its statement afterwards with import_ato_statement"). When-not guidance is present via the duplicate-type refusal 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