Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lodge Business Name Renewal

lodge_business_name_renewal

Validate and lodge a 1- or 3-year renewal for an existing ASIC business name, with dry-run validation before submission.

Instructions

Renew an existing business name with ASIC (BNRENEW) for 1 or 3 years. LIVE cost ≈ $15 service fee + ASIC renewal fee.

request: generalInformation {businessName exactly as registered, abn of the holder, term 1|3, email} and applicant {individual {familyName, givenNames}, declaresTrueAndCorrectIndicator true}. Check the current record first with lookup_abn (businessNames) if unsure of the exact name. dry_run=true (default) validates and returns the payload; dry_run=false lodges -> {requestId, status: "new"}. Then get_business_name_renewal_status / wait_for_request(kind="business_name_renewal") -> 'finished' gives response.businessNameNumber, renewalTo and transactionDocumentUrl.

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

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 already flag a non-read-only, non-idempotent, open-world write, and the description adds real value on top: live cost (≈$15 service fee plus ASIC renewal fee), the default dry_run=true behavior, that dry_run=true returns a payload without lodging, that lodging yields {requestId, status: "new"}, and that field errors come back as a readable list. The only gap is that idempotentHint=false is never addressed — nothing warns against double-lodging or duplicate renewal requests.

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?

Purpose and cost are front-loaded, and the workflow lines are terse and each earn their place. The mid-section is dense — pseudo-schema notation (request/applicant/dry_run) packed into running prose — which costs some scannability, but little is genuinely redundant.

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 write tool with an opaque nested request object and 0% schema coverage, the description supplies the full path: prerequisites, dry-run validation, lodging, status polling, the terminal 'finished' state, and the resulting fields. An output schema exists, so return-value detail is not required, and the brief mention of response fields is a bonus rather than a necessity.

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 description coverage is 0% and the request body is a free-form object with additionalProperties=true, so the description carries the full burden — and it does, enumerating businessName, abn, term 1|3, email, applicant.individual {familyName, givenNames} and declaresTrueAndCorrectIndicator true. It also explains that the exact schema must be fetched via get_request_schema, which is the key semantic an agent needs for an opaque nested payload.

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 with the underlying ASIC transaction code and supported terms: 'Renew an existing business name with ASIC (BNRENEW) for 1 or 3 years.' This clearly separates it from lodge_business_name_registration (a different transaction) and from get_business_name_renewal_status (a read).

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 operational sequence: fetch the request schema first via get_request_schema or the bapi:// resource, verify the registered name with lookup_abn if unsure, then call with dry_run=true to validate, then dry_run=false to lodge, then poll get_business_name_renewal_status or wait_for_request. The when-to-use and what-to-do-first guidance is fully spelled out rather than implied.

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