Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Check Business Name Availability

check_business_name_availability
Read-only

Check a proposed business or trading name against ASIC's name test to see if it is available before registering. Supply a holder name to identify matches against your own company name.

Instructions

Check a proposed BUSINESS (trading) name against ASIC's name test. Free helper.

holder_name: legal name of the entity that will hold the name (e.g. "ACME TRADING PTY LTD"). Strongly recommended: ASIC reports a match on the holder's own company name as "Identical", and with holder_name the response adds availableForHolder (lodge only when true) and marks such objections ownName: true. Response: availability (ASIC code, e.g. Available / Identical / ExistingBN), shortDescription, objections[] {code, level, description, message, matchedNames, ownName}. asicUnavailable: true means "could not check", 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": {
      "name": "<name>"
    },
    "name": "check_business_name_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
holder_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing a genuine failure-mode trap: `asicUnavailable: true` means 'could not check', not 'available'. It also explains the own-name matching rule and the availableForHolder gate, which an agent could not infer from structured fields.

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?

Front-loads the purpose in one short sentence, then scopes the optional parameter. The trailing enumeration of response fields is somewhat redundant against the output schema and adds visual density, but nothing is padded or off-topic.

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

Completeness4/5

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

For a two-parameter read-only check with an output schema, the definition covers the non-obvious edge cases (own-name objections, could-not-check state) that an agent needs to interpret results correctly. The main gap is guidance on what to do next after a non-Available code.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load; it does for holder_name, explaining the format, why it is strongly recommended, and its effect on the response (ownName, availableForHolder). The required `name` parameter gets no explicit definition, relying instead on the purpose sentence.

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 ('Check a proposed BUSINESS (trading) name against ASIC's name test'), and the emphasis on BUSINESS distinguishes it from the sibling check_company_name_availability. An agent can pick between them without opening a schema.

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

Usage Guidelines3/5

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

'Free helper' and the 'lodge only when true' note imply this is a pre-lodgement step before lodge_business_name_registration, but no sibling is named and no when-not condition is given. The routing signal is inferable rather than explicit.

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