Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Company Name Change Status

get_company_name_change_status
Read-only

Retrieve the status of a company name change request, including document number, proposed name, ASIC response, and any validation errors. Use it to track lodged name change outcomes.

Instructions

Status of a name change: {requestId, status, documentNumber, response {companyName, acn, proposedName}, errors}. A request that failed local validation (never reached ASIC) returns only requestId, status and 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_name_change_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=true and openWorldHint=true, so the safety profile is covered. The description does add genuine behavioral value by disclosing a failure variant: a request that failed local validation returns only requestId, status and errors rather than the full response object. It does not cover other status values, terminal states, or error conditions, so the disclosure is partial.

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?

Two tight sentences with no filler. However, the lead position is spent on field enumeration rather than the tool's action, so the front-loading is suboptimal even though nothing is wasted.

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?

An output schema exists, so enumerating return fields is largely redundant, while the genuinely missing pieces — what request_id is and where it comes from, and when to call this versus the lodge tool — are absent. For a status-polling tool whose usefulness depends on the caller knowing how to obtain the ID, that gap matters.

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% and there is one required parameter, request_id. The description mentions a 'requestId' only as part of the returned object, never stating that request_id is the identifier returned by the lodge call, nor its integer format or where to obtain it. With low schema coverage, the description needed to compensate and does not.

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 outcome ('Status of a name change') and is clearly distinguishable from the lodge_* siblings in the catalog by its read-only framing. It is less explicit than a verb-first statement like 'Retrieve the status of a lodged company name change request', but the purpose 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 that this should be called after lodge_company_name_change, and no statement about polling cadence or what to do when status is pending. The only implicit hint is the reference to a request that 'failed local validation', which implies post-lodgement use but never says it.

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