Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lodge Company Registration

lodge_company_registration

Register a new Australian company by lodging ASIC Form 201; validate locally and preview fees before live submission.

Instructions

Lodge ASIC Form 201 — register a new Australian company. LIVE cost ≈ $50 service fee + ASIC registration fee.

request mirrors https://businessapi.com.au/developers/api/company-registrations field-for-field; read bapi://docs/company-registrations (workflow + rules) and bapi://docs/asic-codes (code tables) first. Typical Pty Ltd: companyType APTY, companyClass LMSH, companySubClass PROP, one ORD share class, ≥1 director. Before lodging: check_company_name_availability(name).

dry_run=true (default): validate locally (all "Mandatory IF" rules from the docs) and return the exact JSON that would be posted — show it and the fees to the user. dry_run=false: lodge; returns {requestId, status: "new", billing}. Then wait_for_request(requestId) -> 'finished' gives acn / registrationDate / documentNumber; certificate PDF at GET /company-registrations/{requestId}/certificate, document pack at …/documents.

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

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.8/5.0
Behavior5/5

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

Annotations only declare the generic write/open-world/idempotent profile, but the description adds real cost (~$50 plus ASIC fee), the exact side effect of dry_run=false, the shape of the post-lodgement response, and how to fetch the certificate and document pack afterwards. These are behavioral facts an agent cannot derive from annotations or schema.

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 action and cost, then workflow, then the dry-run fork — a sensible ordering with no filler sentences. It is dense and long, but nearly every clause carries operational information; only the API URL reference is arguably redundant against the resource URIs.

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 two-parameter, high-stakes, nested-object mutation, the definition covers preconditions, cost, dry-run validation, return values, and follow-up retrieval endpoints. Even though an output schema exists, the description still orients the agent to the asynchronous completion flow, which is the risky part.

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 carry the burden — and it does: dry_run's default and local-validation semantics are fully explained, and the opaque `request` object is pointed at get_request_schema plus a resource URI with typical Pty Ltd field values (APTY/LMSH/PROP/ORD). It stops short of documenting individual request fields, but that deferral is deliberate and well-signposted.

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 201 — register a new Australian company' — naming the exact form and jurisdiction. This clearly separates it from siblings like lodge_abn_registration or lodge_business_name_registration without needing to name them.

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?

Gives an explicit pre-flight checklist (read bapi://docs/company-registrations, bapi://docs/asic-codes, call check_company_name_availability, fetch get_request_schema first) and an explicit decision rule for dry_run=true vs false. The post-lodgement path via wait_for_request is also spelled out, leaving nothing to inference.

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