Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Lookup Abn

lookup_abn
Read-only

Validate an Australian Business Number and retrieve ABR entity details, status, GST, and business names before registration, PPSR, or monitoring calls.

Instructions

Validate an Australian Business Number (ABN) and look it up on the ABR.

abn: 11 digits (spaces allowed). Free, read-only, no lodgement. Use this before any registration, PPSR or monitoring call that needs a confirmed ABN / entity name. Response (ABR data, PascalCase keys): Abn, AbnStatus (Active / Cancelled), AbnStatusEffectiveFrom, Acn, EntityName, EntityTypeCode / EntityTypeName, Gst (GST registration date, empty if none), AddressState, AddressPostcode, AddressDate, BusinessName[] (current business names), Message (non-empty when the ABN is unknown or invalid).

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": {
      "abn": "<abn>"
    },
    "name": "lookup_abn"
  }
}

Input Schema

NameRequiredDescriptionDefault
abnYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing cost ('Free'), that no lodgement occurs, and crucially the failure semantics: 'Message (non-empty when the ABN is unknown or invalid)'. It also notes PascalCase keys and the Gst field being empty when unregistered — practical quirks an agent would otherwise discover by trial.

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?

Front-loaded with purpose, then the input constraint, then usage, then the response shape — a logical order with no filler. The response enumeration is dense but every field listed (AbnStatus, Gst, BusinessName[], Message) is one an agent may need to branch on.

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 read tool with annotations and an output schema, this is close to complete: purpose, input format, invocation timing, and error signalling are all present. The response field list partly duplicates what the output schema already provides, but it adds the empty/non-empty semantics that matter.

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 schema only says type string, so the description must carry the parameter — it does, specifying '11 digits (spaces allowed)', which tells the agent both the format and the normalization tolerance. It does not say what happens with an invalid-format ABN beyond the Message field, leaving one small gap.

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 — 'Validate an Australian Business Number (ABN) and look it up on the ABR' — and the ABN-vs-entity framing makes it distinguishable from the ACN lookup sibling. An agent knows exactly what this tool returns (ABR entity data) without opening the schema.

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?

Explicitly says to use it 'before any registration, PPSR or monitoring call that needs a confirmed ABN / entity name', which names concrete downstream tool families. It does not explicitly exclude cases (e.g. when a user supplies an ACN instead, use lookup_acn), so it stops short of full when/when-not coverage.

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