Skip to main content
Glama
Sign In
Beeswax Shares MCP Server

Beeswax Shares MCP Server

by steamau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List ATO imports

list_ato_imports
Read-only

Lists statement imports into an ATO account newest first, showing file, covered dates, line changes, balance agreement, and undo readiness to help find the import ID to undo.

Instructions

List the statement imports into an ATO account, newest first: file, dates covered, lines created / updated / unchanged, whether the balance agreed with the ATO's afterwards, and whether each can be undone (can_undo, undo_blockers). Use to find the import_id for undo_ato_import.

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>",
      "ato_account_id": "<ato_account_id>"
    },
    "name": "list_ato_imports"
  }
}

Input Schema

NameRequiredDescriptionDefault
fund_idYesFund ID (discover via whoami or list_funds)
ato_account_idYesATO account ID (find via list_ato_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.4/5.0
Behavior4/5

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

The readOnlyHint annotation already signals this is a safe read, and the description adds useful behavioral detail: results are newest first and include file, covered dates, line counts, balance agreement, and undoability with can_undo/undo_blockers. It does not mention pagination or permissions, but it discloses far more than the annotation alone.

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?

It is a single sentence with the main action and scope front-loaded, followed by the return fields and the recommended follow-up use. Every clause carries information and nothing is repetitive.

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 usefully explains what the returned imports include, including undo blockers. It is nearly complete for a simple list tool; adding pagination or empty-result behavior would make it fully self-contained.

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 have descriptions pointing to whoami/list_funds and list_ato_accounts. The description does not add any additional meaning about fund_id or ato_account_id, so the baseline of 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?

The description states a specific verb and resource: list statement imports into an ATO account. It also includes scope and ordering ('newest first') and names the sibling tool it feeds into ('undo_ato_import'), making it clearly distinguishable from import_ato_statement and undo_ato_import.

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?

It explicitly says to use this tool to find the import_id for undo_ato_import, which gives the agent a concrete selection condition versus the undo operation. No exclusion conditions are needed for a simple read-only lookup tool of this kind.

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