Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lookup Acn

lookup_acn
Read-only

Validates a 9-digit Australian Company Number (ACN) and retrieves ASIC company details, including name, status, type, registration date, and addresses.

Instructions

Validate an Australian Company Number (ACN) and look the company up on ASIC.

acn: 9 digits (spaces allowed). Free, read-only. Response (ASIC data): name, type (e.g. Australian Proprietary Company), class, subClass, status (Registered / Deregistered …), incorporationState, registrationDate, addresses[] {type, address, suburb, postcode, state}.

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": {
      "acn": "<acn>"
    },
    "name": "lookup_acn"
  }
}

Input Schema

NameRequiredDescriptionDefault
acnYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 description's 'read-only' is redundant; however 'Free' adds genuine cost context and 'on ASIC' clarifies the external data source. It omits failure behavior (what happens on an invalid or unregistered ACN), rate limits, and any latency or availability caveats, and the response field list largely duplicates the existing 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.

Conciseness4/5

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

Front-loaded with the action, then the parameter rule, then cost/mode, then response contents – a logical order with no filler sentences. The Response paragraph enumerates fields that the output schema already defines, which is the one place wording does not fully earn its space.

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 single-parameter lookup with an output schema present, the description covers input format, cost, and data source, which is most of what an agent needs. What is missing is error/edge-case behavior for invalid or unknown ACNs, the one gap that keeps it from being complete.

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% and the input schema declares only a bare string, so the description carries the burden and does so well: 'acn: 9 digits (spaces allowed)' gives both the length constraint and a tolerance rule the schema lacks. It stops short of stating what an invalid format produces, so it is not a 5.

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: 'Validate an Australian Company Number (ACN) and look the company up on ASIC.' The ACN scope implicitly separates it from the sibling lookup_abn, but no explicit routing sentence differentiates the two, so an agent must infer the split from the resource name.

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?

Usage is only implied by the verb 'Validate...and look up', and 'Free, read-only' gives useful cost/permission context. There is no explicit statement of when to prefer this over lookup_abn or an entity-snapshot tool, and no exclusions or prerequisites are given.

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