Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Company Deregistration Status

get_company_deregistration_status
Read-only

Check the status of a company deregistration request by request ID and retrieve details such as company name, ACN, company type, and deregistration date.

Instructions

Status of a deregistration: {response: {requestId, status, documentNumber, info {companyName, acn, companyType, companyClass, companySubClass, jurisdictionOfRegistration, dateOfDeregistration}}, 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_company_deregistration_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/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's burden is to add context such as polling behavior, status value semantics, or error conditions. Instead it only enumerates return fields, and even labels an errors element without saying what errors mean or when they appear.

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

Conciseness2/5

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

The single sentence is a raw, unformatted dump of the response JSON shape, awkwardly line-broken mid-object. It spends its entire length on structure rather than purpose, and the content duplicates the output schema.

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

Completeness2/5

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

For a polling-style read tool with an output schema that already defines the response, the description adds almost nothing and omits the operational facts an agent needs: where request_id comes from, how often to poll, and what status values mean. The one thing it does cover, the response shape, is already structured data.

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?

There is one parameter, request_id, with 0% schema description coverage, and the description never mentions it. A caller gets no hint that the id comes from the lodging call or whether it is the same requestId echoed in the response — a gap that matters for the only required input.

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

Purpose2/5

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

"Status of a deregistration" largely restates the tool name and title rather than stating a distinct verb+resource action. It never says what a deregistration is here (an ASIC company deregistration request) or how it differs from the many sibling status-polling tools such as get_request_status or get_asic_form_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: no mention that this should be called after lodge_company_deregistration, no note on polling cadence or terminal states, and no pointer to alternatives. The agent must infer the whole workflow from the sibling list.

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