Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Asic 484 Form Status

get_asic_484_form_status
Read-only

Check the status of an ASIC Form 484 lodgement using its request ID and retrieve the current status, document number, company name, and ACN.

Instructions

Status of a Form 484 lodgement: {response: {requestId, status, documentNumber, info: {companyName, acn}}, 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": {
      "request_id": "<request_id>"
    },
    "name": "get_asic_484_form_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is lighter. It adds that a response may carry an errors collection alongside the payload, which hints at partial-failure handling, but says nothing about polling, eventual consistency, or what an unknown request id yields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded line with no filler, but it spends its only sentence on a pseudo-schema rendering of the return shape, which is largely redundant.

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?

An output schema exists, so the description needn't restate the response shape, and the space used for it would be better spent on the request id. For a simple one-parameter read it is minimally adequate, but it omits the linkage to the lodge call that produces the id.

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?

The single parameter request_id has 0% schema description coverage, so the description must carry the meaning and does not. It never states that request_id is the identifier returned by lodge_asic_484_form, nor its format or valid range.

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?

The description names a specific resource and operation: the status of a Form 484 lodgement. It is clear what the tool reads, but it offers no differentiation from similar siblings such as get_asic_form_status or get_request_status.

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 when-to-use guidance at all, nor any mention of alternatives. An agent cannot tell from this text why it would pick this over get_asic_form_status or the generic get_request_status.

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