Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lodge Company Name Change

lodge_company_name_change

Lodge ASIC Form 205A to change a registered company’s name. Validate and submit the request, with dry-run support for checking the payload before lodgement.

Instructions

Lodge ASIC Form 205A — change a registered company's name. LIVE: service fee + ASIC fee (paymentMethod DDEB or INV).

Before lodging: check_company_name_availability(proposedName). request = generalInformation {companyName, acn, companyType, proposedName (with legal elements), meetingDate, meetingResolutionText (the special resolution), paymentMethod DDEB|INV, optional acnName*/nameReserved*/nameIdentical* flags}, signatory {individual, role DIR|SEC…, dateSigned, declaration true}, admin {manualReviewIndicator}. Read bapi://docs/asic-agent-forms. Requires registered-agent onboarding for the company. dry_run=true (default) validates and returns the payload; dry_run=false lodges -> {requestId, status: "sent"}. Then get_company_name_change_status / wait_for_request(kind="company_name_change") -> finished; certificate PDF at GET /company-name-changes/{requestId}/certificate (binary, outside MCP).

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

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?

Beyond the annotations (which only state it is a non-readonly, non-idempotent, open-world write), the description discloses that this is a LIVE operation incurring a service fee plus ASIC fee via paymentMethod DDEB or INV. It explains the crucial dry_run=true default (validate only, returns payload) versus dry_run=false (actually lodges -> {requestId, status: "sent"}), and notes the certificate is binary and outside MCP.

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?

Content is front-loaded (action, fee model, then prerequisites, then payload shape, then follow-up) with no filler sentences. It is dense and parenthetical, which is justified by the tool's complexity, though the shorthand asterisk notation slightly hurts scannability.

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 live, fee-incurring, nested-payload form lodgement, the definition covers prerequisites, dry-run semantics, payment methods, return shape, follow-up polling, certificate retrieval, the schema-fetch escape hatch, and how validation errors surface. Nothing an agent needs to invoke it safely appears to be 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% with a free-form nested object (additionalProperties: true), so the description carries the full burden and largely does: it enumerates generalInformation fields (companyName, acn, companyType, proposedName, meetingDate, meetingResolutionText, paymentMethod, optional flags), signatory fields, and admin.manualReviewIndicator. The wildcard flags (acnName*, nameReserved*, nameIdentical*) are gestured at rather than explained, and it defers exact structure to get_request_schema, which keeps it below a 5.

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?

"Lodge ASIC Form 205A — change a registered company's name" names the specific form, the verb (lodge), and the exact resource mutation, so an agent can distinguish it from lodge_company_registration, lodge_business_name_registration, and other ASIC form tools without opening a schema.

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?

It gives an explicit prerequisite chain: run check_company_name_availability(proposedName) before lodging, read bapi://docs/asic-agent-forms, and confirm registered-agent onboarding for the company. It also names the follow-up path (get_company_name_change_status / wait_for_request) and where the certificate lives, so the agent knows both when to call it and what to do afterwards.

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