Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Reopen a confirmed SMSF return section

reopen_smsf_return_section

Undo a section confirmation on an SMSF return so its figures can be edited again, without changing the figures themselves. Use before a return is finalised.

Instructions

Undo a section confirmation so its figures can be edited again (drops that section's confirmation snapshot; the figures themselves are unchanged). Not possible once the return is finalised — reopening a finalised return is done in the web app.

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>",
      "smsf_return_id": "<smsf_return_id>",
      "section_key": "<section_key>"
    },
    "name": "reopen_smsf_return_section"
  }
}

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
section_keyYesReturn section key, e.g. "fund_information", "income", "deductions", "tax_calc", "assets_liabilities", or "members" for the member information statement (the keys get_smsf_return lists)
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.
smsf_return_idYesSMSF return ID (from get_smsf_return / create_smsf_return)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing exactly what the write removes — the section's confirmation snapshot — and explicitly that the underlying figures are untouched. It also surfaces a hard precondition (return must not be finalised) that annotations cannot express, which is the essential behavioral fact for this mutation.

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 short sentences: the primary effect and its guarantee first, then the limitation with a redirect. No redundant restatement of the name or title and no filler.

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 five-parameter mutation with no output schema, the description covers purpose, side effect, and precondition, and the schema covers parameter semantics and idempotency. Minor omissions remain — behavior when the section was never confirmed, and what the call returns — but nothing critical to correct invocation is missing.

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 description coverage is 100%, so every parameter including fund_id, smsf_return_id, section_key, reasoning, and external_ref is already documented in the schema. The description adds no parameter-level meaning, 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 ('Undo a section confirmation') plus the effect ('so its figures can be edited again'), which cleanly distinguishes it from the sibling confirm_smsf_return_section. An agent can identify the inverse operation without opening any 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?

Explicitly states the condition under which the tool is unusable ('Not possible once the return is finalised') and where to go instead ('reopening a finalised return is done in the web app'). It does not name confirm_smsf_return_section as the counterpart, but the implied workflow (confirm to lock, reopen to edit) is clear.

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