Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lodge Business Name Registration

lodge_business_name_registration

Register a business (trading) name with ASIC after validating the request; defaults to a dry run, then lodges live to return a request ID for status tracking.

Instructions

Register a business (trading) name with ASIC (BNREG). LIVE cost ≈ $15 service fee + ASIC fee (1 or 3 years).

request mirrors https://businessapi.com.au/developers/api/business-name-registrations; read bapi://docs/business-name-registrations first. Holder types: IND, IB (companies), PTSH, USTR, JV. Before lodging: check_business_name_availability(name, holder_name) and require availableForHolder == true. paymentMethod "card" -> after lodging, get_business_name_registration_status returns an ASIC payment link the payer must open; "invoice" -> ASIC emails an invoice (pay within 10 days).

dry_run=true (default): validate and return the payload. dry_run=false: lodge -> {requestId, status: "new"}. Then get_business_name_registration_status / wait_for_request(kind="business_name").

request is a JSON object. Fetch its exact schema first with get_request_schema("business_name_registration") (or read resource bapi://schemas/business_name_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_business_name_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.9/5.0
Behavior5/5

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

Annotations only declare it as a non-read-only, open-world, non-idempotent mutation; the description adds the live costs (~$15 + ASIC fee for 1 or 3 years), the two payment flows and their consequences (ASIC payment link vs emailed invoice with 10-day window), the dry-run validation behavior, and the shape of the lodge response ({requestId, status: "new"}). It also states that field errors come back as a readable list, which annotations cannot convey.

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 cost, then layered into prerequisites, payment, dry-run, and follow-up with backticked identifiers. Dense and mostly earning its place, though the status tool is mentioned twice and the block is long enough that an agent must read all of it to catch the ordering constraint.

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 complex, non-idempotent, open-world mutation with a nested free-form payload and an output schema (so return shape needn't be re-explained), the description covers gating preconditions, cost, payment handling, dry-run semantics, and post-lodging polling. Nothing essential to calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and a free-form `request` object, the description does the heavy lifting: it lists holder types (IND, IB, PTSH, USTR, JV), points to the exact API doc and to get_request_schema("business_name_registration") / bapi://schemas/business_name_registration for the full payload schema, and fully defines dry_run's two modes and default.

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 ('Register a business (trading) name with ASIC (BNREG)') and immediately distinguishes itself from siblings like lodge_business_name_renewal and lodge_company_registration by naming BNREG. The cost note further pins down the exact transaction.

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?

Explicit prerequisites: read bapi://docs/business-name-registrations, call check_business_name_availability and require availableForHolder == true before lodging. Payment branch ('card' vs 'invoice') and the dry_run=true default vs dry_run=false path are spelled out, and the follow-up tools (get_business_name_registration_status, wait_for_request) are named.

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