Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lodge Asic 484 Form

lodge_asic_484_form

Validate and lodge ASIC Form 484 to change company details such as registered office, officeholders, share issues or cancellations, and ultimate holding company under a registered-agent account.

Instructions

Lodge ASIC Form 484 — Changes to Company Details — for a company managed under your registered-agent account.

One form can combine any of: registeredOffice / principalPlaceOfBusiness address change, officeHolders (appointments, cessations, name/address changes), shareIssue or shareCancellation (both need shareStructure + members), ultimateHoldingCompany, concessionalFees, annexures. Always needs generalInformation {companyName, acn} and signature {name, role DIR|SEC|ALT, date within the last 6 months, declaresTrueAndCorrectIndicator true}. Read bapi://docs/asic-484-forms first for the status / holdingStatus / cancellationProvision codes and the V455 share-totals rule (checked locally). The server upper-cases all string values (ASIC requirement). ASIC charges late fees when a change is notified more than 28 days after it took effect. Billed as a registered-agent form (Pro plan includes 2,500 forms/month).

dry_run=true (default) validates and returns the payload; dry_run=false lodges -> {response: {requestId, documentNumber, documentUrl}}. Then get_asic_484_form_status / wait_for_request(kind="asic_484").

request is a JSON object. Fetch its exact schema first with get_request_schema("asic_484_form") (or read resource bapi://schemas/asic_484_form), build the object, then call this tool; field errors come back as a readable list.

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": {
      "request": "<request>"
    },
    "name": "lodge_asic_484_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
requestYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag a non-read-only, open-world, non-idempotent write, and the description adds real value beyond them: server-side upper-casing of strings, the 28-day late-fee trigger, local validation of the V455 share-totals rule, billing impact (2,500 forms/month on Pro), and the two-phase dry_run-then-lodge semantics. The return shape and post-lodge follow-up tools are also spelled out.

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-loads the identity and scoping, then prerequisites, then dry_run semantics, then the schema-fetch instruction — a sensible order for an agent. It is dense but a few fragments (the Pro-plan monthly allotment) are marginal for call decisions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a high-complexity, nested-payload write tool with an output schema present, the description covers inputs, validation, side effects, costs, return values, and the follow-up status/wait flow. Nothing an agent needs before invoking it is missing.

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 0% for a nested free-form `request` object, so the description must compensate and largely does — it enumerates the allowed change blocks and the mandatory generalInformation/signature sub-fields, and describes dry_run's default and effect. Exact field-level schema is deliberately deferred to get_request_schema, which is a reasonable but incomplete substitute within the description itself.

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?

Names a specific verb (lodge) and a specific resource (ASIC Form 484 — Changes to Company Details), and scopes it to companies under the caller's registered-agent account. Because the form number is named, an agent can distinguish it from siblings like lodge_asic_361_form / lodge_asic_362_form without opening schemas.

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?

Gives the when-to-use context (registrable change types combinable in one form), prerequisites (generalInformation + signature fields), and pre-call steps (read bapi://docs/asic-484-forms, fetch schema via get_request_schema). It stops short of explicitly routing away from alternatives such as lodge_company_name_change or the 361/362 forms, so there are no stated exclusions.

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