Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lodge Company Deregistration

lodge_company_deregistration
Destructive

Lodge ASIC Form 6010 to voluntarily deregister a company, validating all required s.601AA declarations before submission; dry-run by default.

Instructions

Lodge ASIC Form 6010 — VOLUNTARY DEREGISTRATION of a company (irreversible once ASIC deregisters). LIVE: service fee + ASIC fee.

All six s.601AA declarations must be true (members agree, not trading, assets < $1,000, fees paid, no liabilities, no legal proceedings) — the validator refuses otherwise. request = general {companyName, acn, paymentMethod DDEB|INV}, declarations, applicant (the company as organisation + role, or an individual), nominee {individual, address} to receive ASIC correspondence, signatory {individual, role, dateSigned, declaration true}. Read bapi://docs/asic-agent-forms. dry_run=true (default) validates and returns the payload; dry_run=false lodges -> {response: {requestId}}. Then get_company_deregistration_status / wait_for_request(kind="company_deregistration") -> finished with info.dateOfDeregistration. Transmission log: GET /company-deregistrations/{requestId}/logs (call_endpoint).

request is a JSON object. Fetch its exact schema first with get_request_schema("company_deregistration") (or read resource bapi://schemas/company_deregistration), 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_company_deregistration"
  }
}

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 declare destructive/openWorld/not-idempotent, but the description adds the crucial business context annotations cannot: deregistration is irreversible once ASIC acts, fees are charged live, and the validator rejects the call unless all six declarations hold. It also discloses the dry-run default behavior and where the transmission log lives.

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 highest-stakes facts (form number, irreversibility, fee) before schema detail, and the follow-up flow comes last. Dense and mostly earned, though the single-block prose of nested field lists is harder to scan than it needs to be.

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 destructive, nested-schema, live-fee tool this covers everything an agent needs: preconditions, dry-run ladder, required schema-fetch step, and the status/wait path to a dateOfDeregistration result. The concrete success shape ({response: {requestId}}) is a useful bonus even though an output schema exists.

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%, so the description must compensate nearly entirely — and it does, outlining request fields (companyName, acn, paymentMethod DDEB|INV), declarations, applicant, nominee and signatory with their sub-fields, plus the dry_run semantics. It stops short of enumerating every leaf field but explicitly routes to get_request_schema("company_deregistration") / bapi://schemas/company_deregistration for the exact shape, which is the right instruction for a deeply nested object.

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 ("Lodge ASIC Form 6010 — VOLUNTARY DEREGISTRATION of a company") and immediately flags irreversibility and cost. This is clearly distinguishable from lodge_company_registration and lodge_company_name_change 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?

Gives strong operational routing: dry_run=true (default) validates and returns payload; dry_run=false lodges, then get_company_deregistration_status / wait_for_request(kind="company_deregistration") for completion, plus the logs endpoint. It also states preconditions — all six s.601AA declarations must be true or the validator refuses. It stops short of explicitly naming when to prefer an alternative path, so not a full 5.

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