Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Request Status

get_request_status
Read-only

Check the status of a lodged company, ABN, tax, ASIC, or business-name request by request ID. Retrieve progress, validation errors, warnings, or final registration details as it moves to completion.

Instructions

Poll any lodgement (company / ABN / tax / business-name registration, ASIC forms, deregistration…) by requestId.

Lifecycle: new -> transmission ok -> validation ok | validation failed -> manual review -> finished | rejected. On 'validation failed' / 'rejected' read errors[] ({details, target}); on 'manual review' read warnings; on 'finished' the result (e.g. acn, abn, dateOfRegistration, documentNumber) is in response (ABN: info). Use wait_for_request to block until a terminal state; use webhooks in production.

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_request_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

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the full state machine and what each terminal/non-terminal state exposes (errors[] with {details, target} on failure states, warnings on manual review, result fields such as acn/abn/dateOfRegistration/documentNumber in `response`, `info` for ABN). The production webhook advice also flags polling as not the intended long-run pattern.

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

Conciseness5/5

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

Three compact blocks — purpose, lifecycle, per-state guidance plus alternatives — with the core action front-loaded and no filler. The parenthetical field names are dense information rather than padding.

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?

An output schema exists, so return values need not be enumerated; the description nonetheless maps states to the fields worth reading, and it covers failure handling, terminal detection, and production alternatives. For a single-parameter read tool this leaves nothing an agent needs missing except the provenance of request_id.

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

Parameters3/5

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

Schema description coverage is 0% for the single integer request_id, so the description must carry the burden, and it only adds that the ID refers to a lodgement — it never says where the requestId comes from (presumably a lodge_* response) or what an invalid ID does. The state-to-field mapping is useful, but the sole parameter remains under-explained.

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 ('Poll any lodgement ... by requestId') and enumerates the covered lodgement types (company / ABN / tax / business-name registration, ASIC forms, deregistration), which makes clear it is the generic status reader rather than the type-specific siblings. It also names wait_for_request as the blocking alternative, so an agent can distinguish the two without opening either schema.

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?

Explicitly routes usage: use this to poll, use wait_for_request to block until a terminal state, and use webhooks in production. The lifecycle sequence ('new -> transmission ok -> validation ok | validation failed -> manual review -> finished | rejected') tells the agent when continued polling is pointless, which is exactly the decision it needs to make.

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