Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Request Asic Account Transactions

request_asic_account_transactions
Idempotent

Request an ASIC account transaction report for a date range to review invoices, fees, direct debits, late fees, and payments; returns a request ID for status tracking.

Instructions

Request ASIC Form RA52 — a report of all transactions on your registered-agent ASIC account for a period (invoices, fees, direct debits, late fees, payments). Dates YYYY-MM-DD, end_date ≤ today. Billed as a registered-agent form (no legal effect). Returns {response: {requestId, documentNumber}}; then get_asic_form_status(form="ra52") / wait_for_request(kind="asic_ra52") -> finished with response.records[] {date, legend (Table 0019, e.g. Invoice, Direct Debit, Late Fee), status (Table 0020, e.g. Outstanding, Fully Allocated), value / outstandingValue (signed cents as strings, "+49500" = $495.00), reference, acn}.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "request_asic_account_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
end_dateYes
start_dateYes
include_prior_outstandingNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the billing model, the absence of legal effect, the two-step async commit pattern, and the validation constraint end_date ≤ today. Annotations already cover openWorldHint and idempotentHint, so the description's job is context, which it delivers. It does not explain what happens on re-request or how dry_run changes behavior.

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 purpose and constraint, then the return/workflow detail. It is dense but nearly every clause carries information; the main inefficiency is restating the records[] field breakdown, which largely duplicates the existing output schema.

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?

The async follow-up path, date validation, and return shape make this callable without extra exploration, and an output schema exists so return details are a bonus. The remaining gap is the two undocumented optional flags, which an agent cannot reason about from the description alone.

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 0%, so the description must carry the burden: it documents start_date/end_date format (YYYY-MM-DD) and a validation rule, which is valuable. However, dry_run and include_prior_outstanding are never mentioned, and the latter materially affects the outstandingValue data described in the return shape.

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: request ASIC Form RA52, a transaction report for a registered-agent ASIC account, and enumerates the transaction types it covers (invoices, fees, direct debits, late fees, payments). This clearly separates it from the lodge_* siblings and from the status/polling tools it names.

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 explains the async workflow: this tool only kicks off the request and returns {requestId, documentNumber}, after which the agent must use get_asic_form_status(form="ra52") or wait_for_request(kind="asic_ra52"). It also flags the billing consequence (registered-agent form, no legal effect). It does not say when to prefer this over requesting other ASIC forms, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.