Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lodge Asic 361 Form

lodge_asic_361_form

Lodge ASIC Form 361 to notify that your registered-agent account ceases to act for a company. Preview the payload with a dry run, then submit to receive a request ID and document number.

Instructions

Lodge ASIC Form 361 — YOUR registered-agent account ceases to act for a company (agent-initiated).

request = generalInformation {companyName, acn}, signature {name, role AGT, date, agentAuthorisedIndicator true, declaration true}. Billed as a registered-agent form. dry_run=true (default) returns the payload; dry_run=false lodges -> {response: {requestId, documentNumber, documentUrl}}. Then get_asic_form_status(form="361") / wait_for_request(kind="asic_361").

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

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

Goes well beyond the annotations by disclosing billing ('Billed as a registered-agent form'), the exact dry_run default and its two outcomes (payload vs. lodgement), the shape of the lodgement response (requestId, documentNumber, documentUrl), and how field errors surface as a readable list. That is precisely the operational context the readOnlyHint/openWorldHint flags 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, then the payload contract, then the execution/verification path — a sensible order. Dense but nearly every line carries information; only the parenthetical schema-resource alternative slightly duplicates the get_request_schema instruction.

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 billing-relevant, schema-indirected mutation tool it covers prerequisite, payload construction, dry-run behavior, error handling, and the status-check follow-up. The presence of an output schema means the response detail is a bonus rather than a requirement, so nothing material is 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?

With 0% schema description coverage and an opaque free-form `request` object, the description compensates by sketching the required structure (generalInformation {companyName, acn}, signature {name, role AGT, date, agentAuthorisedIndicator true, declaration true}) and explaining dry_run's default and effect. It still defers exact field definitions to the separate schema resource rather than fully specifying them inline, so a 4 rather than 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?

States a specific verb and resource — lodging ASIC Form 361 — and defines its legal effect precisely: 'YOUR registered-agent account ceases to act for a company (agent-initiated).' The form number plus the agent-initiated qualifier separates it from the sibling lodge_asic_362_form / lodge_asic_484_form filings without needing to open 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 an explicit prerequisite and follow-up chain: fetch the schema with get_request_schema("asic_361_form") or the resource URI first, then call, then poll via get_asic_form_status(form="361") / wait_for_request(kind="asic_361"). It does not state when a different form (362/484) would be the correct choice instead, which is the remaining gap.

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