Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lodge Asic 362 Form

lodge_asic_362_form

Lodge ASIC Form 362 to appoint or cease a company’s registered agent, linking it to your agent account for other ASIC form lodgements. Preview payloads with dry run before submission.

Instructions

Lodge ASIC Form 362 — a company appoints (type A) or ceases (type C) your registered agent number (company-initiated).

Appointing links the company to your agent account, which the other ASIC form tools (484, 205A, 6010 …) need. request = generalInformation {companyName, acn, type A|C}, signature {name, role DIR|SEC, date, declaration true}. dry_run=true (default) returns the payload; dry_run=false lodges -> {response: {requestId, documentNumber, documentUrl}}. Then get_asic_form_status(form="362") / wait_for_request(kind="asic_362").

request is a JSON object. Fetch its exact schema first with get_request_schema("asic_362_form") (or read resource bapi://schemas/asic_362_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_362_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.7/5.0
Behavior4/5

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

Annotations declare it is a non-read-only, open-world, non-idempotent but non-destructive mutation; the description adds the crucial behavior that dry_run defaults to true and only dry_run=false actually lodges the form, plus the shape of the successful response. It does not discuss permissions, failure modes beyond field errors, or reversibility of a type C cessation, which would round it 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-loaded with purpose and the A/C distinction, then prerequisites, then parameter detail, then follow-ups — a sensible order with no filler. The arrow shorthand and parenthetical asides make it dense to parse in places, but no sentence is wasted.

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?

Given an output schema exists, the description needn't explain return values, yet it sketches the response envelope and names the status-check tools. Combined with the request structure and dry-run semantics, an agent has everything needed to invoke this correctly on the first try.

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?

Schema coverage is 0% and the request is a free-form nested object, so the description does the heavy lifting: it enumerates generalInformation {companyName, acn, type A|C} and signature {name, role DIR|SEC, date, declaration true}, and explains dry_run's default and effect. This is exactly the compensation a 0%-coverage nested schema needs.

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 362') plus the two distinct sub-operations (type A appoints, type C ceases a registered agent number). It also distinguishes the tool from sibling forms (484, 205A, 6010) by explaining the dependency relationship.

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 explicit when-to-use context ('Appointing links the company to your agent account, which the other ASIC form tools ... need'), names the prerequisite step (fetch schema via get_request_schema or the bapi:// resource), and names the follow-up tools (get_asic_form_status, wait_for_request). Very little is left to inference.

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