apibase

ABR — Australian Business ABN Lookup

abr.business.abn_lookup

Read-onlyIdempotent

Resolve an Australian Business Number (ABN) to full entity details using the official Australian Business Register (ABR). Returns entity name, entity type (company, sole trader, partnership, government entity, etc.), ABN status (Active/Cancelled), GST registration date, registered address state and postcode, ACN (if a company), and all registered trading/business names. Covers 15M+ ABNs across all Australian states and territories. Data is live from the ATO-managed national register. Source: ABR, free registration, commercial use permitted.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`abn`	Yes	Australian Business Number (ABN) — 11-digit numeric identifier, spaces optional (e.g. "33 051 775 556" or "33051775556")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds context beyond these: data is 'live from the ATO-managed national register', covers '15M+ ABNs', and notes 'free registration, commercial use permitted'. It also discloses the type of information returned, which is valuable for an agent.

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?

The description is moderately sized but every sentence adds value: purpose, return fields, coverage, and data source/licensing. It is well-organized and front-loaded with the core purpose.

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 lookup tool with an output schema present, the description covers the essential context: what it does, what it returns, coverage scope, data freshness, and licensing. Nothing critical is missing for an agent to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100% for the single 'abn' parameter, including format examples. The description does not add new parameter semantics beyond what the schema already provides, so a baseline of 3 is appropriate.

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?

The description starts with a specific verb + resource: 'Resolve an Australian Business Number (ABN) to full entity details'. It clearly distinguishes the tool from siblings like acn_lookup and name_search by focusing on ABN-based resolution and explicitly listing the returned fields.

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?

The context of use is clear: when you have an ABN and need official entity details, this tool is appropriate. It does not explicitly name alternatives or exclusion conditions, but the description implies the sole use case (ABN lookup) without ambiguity.

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

All apibase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.