Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Business Name Registration Status

get_business_name_registration_status
Read-only

Check the status of a business name registration by request ID, showing payment links, completion documents, cancellations, or rejection reasons.

Instructions

Status of a business-name registration. Statuses: new -> … -> "wating ASIC CC payment" (card: response has transactionPaymentUrl + transactionFee; the payer must open the link) -> finished (certificateUrl / receiptNumber, or transactionDocumentUrl for invoice payment). "cancelled" = payment link expired/declined: call refresh_business_name_payment_link, never re-lodge. "rejected" with errors["00133"] = name not available.

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

A3.8/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 adds a full state machine (new -> payment waiting -> finished), names the response fields per state (transactionPaymentUrl, transactionFee, certificateUrl, receiptNumber, transactionDocumentUrl), and maps errors["00133"] to a specific meaning. This is behavioral context that no annotation or schema field conveys.

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?

Dense but front-loaded: purpose first, then a compact status chain with per-state payload notes and one recovery rule. Every clause carries information, though the arrow-chain formatting and the typo'd status string 'wating ASIC CC payment' make it slightly harder to scan than a short bulleted list would.

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 return-value explanation is a bonus, and the status/payload mapping is thorough. The gap is procedural: an agent still does not know how to obtain request_id or how this differs from the other get_*_status siblings, which matters for a polling tool in a large sibling set.

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 schema carries no meaning at all. The description never explains what request_id is or where it comes from (presumably the lodge call's return), leaving the only required input undefined.

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 first sentence names the specific resource (a business-name registration) and the verb is implicit but unambiguous (get status). It is distinguishable from get_business_name_renewal_status by the resource noun, though the description never explicitly contrasts the two status tools in the sibling list.

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

Usage Guidelines4/5

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

Gives a concrete routing rule for one branch: on 'cancelled', call refresh_business_name_payment_link and 'never re-lodge', which is an explicit exclusion with a named alternative. It does not say when to prefer this over get_request_status or get_business_name_renewal_status, so general selection guidance is only partial.

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