Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Check Company Name Availability

check_company_name_availability
Read-only

Verify ASIC availability of a proposed company name, including legal elements, before company registration or a name reservation.

Instructions

Check whether a proposed COMPANY name (including legal elements, e.g. "ACME PTY LTD") is available with ASIC. Free helper. Call this before lodge_company_registration or a name change / reservation.

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_company_name_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, so the bar is lower. The description still adds genuine context beyond them: the check runs against ASIC as an external authority and is a 'Free helper', which matters for agent cost decisions. It says nothing about latency, rate limits, or reliability of the result, and return values are covered by the output schema.

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?

Two sentences, both earning their place: the first defines the check and its input format, the second gives the free-helper note and call ordering. Front-loaded with the core action and no filler.

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?

For a single-parameter read-only availability check with an output schema, this is complete: input format, external system, cost, and call ordering are all covered. An agent can invoke it correctly without further information.

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?

One parameter with 0% schema description coverage, so the description carries the burden. It does so usefully by specifying the accepted format including legal elements, with the worked example 'ACME PTY LTD'. It does not mention normalization, casing, or what happens with an invalid/empty name.

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?

States a specific verb and resource ('Check whether a proposed COMPANY name ... is available with ASIC'), and the capitalized COMPANY plus the sibling check_business_name_availability makes the company-vs-business scope inferable. It stops short of explicitly saying it does not cover business names, so differentiation is implied rather than stated.

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 explicit sequencing guidance: call this before lodge_company_registration or a name change/reservation. That is a real when-to-use rule tied to named downstream tools. It does not state when-not-to-use or address the company-vs-business choice directly.

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