Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Asic Form Status

get_asic_form_status
Read-only

Retrieves the lodgement status of an ASIC Form 361, 362, or RA52 using its request ID, returning the request status, document number, company and ACN details, and any errors.

Instructions

Status of a Form 361 / 362 / RA52 lodgement: {response: {requestId, status, documentNumber, info {companyName, acn, type?}, records? (RA52)}, errors}.

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": {
      "form": "<form>",
      "request_id": "<request_id>"
    },
    "name": "get_asic_form_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
formYes
request_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds the response envelope shape and an errors field, but says nothing about authentication, what happens with an unknown or expired requestId, or how source-record availability differs between forms.

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?

A single compact sentence with the resource and form scope front-loaded and no filler. The trailing response-shape dump is partly duplicative of the output schema, which costs it a point but not much more.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with an output schema, the definition is minimally adequate. The critical gap is the unexplained request_id and the absence of any usage framing that would tell the agent when this call is the correct one versus the many other status tools in the catalog.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter burden. It clarifies the 'form' parameter by listing the three accepted values, but leaves 'request_id' completely unexplained — the agent is not told it is the ID returned by a prior lodgement call or what format it takes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (lodgement status) and enumerates the exact forms covered (361, 362, RA52), which distinguishes it from the sibling get_asic_484_form_status. It is a noun phrase rather than a verb, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no mention of prerequisites or sequencing (e.g. call after lodge_asic_361_form), and no routing to alternatives such as get_request_status. The post-lodgement context is only weakly implied by the word 'lodgement'.

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