Skip to main content
Glama
Australian Accounting MCP

Australian Accounting MCP

Test an ABN check digit

validate_abn
Read-onlyIdempotent

Validate an Australian Business Number by check-digit arithmetic, returning valid, invalid, or malformed; spaces are ignored, and registration status is not confirmed.

Instructions

Test an ABN against the check digit arithmetic ABN Lookup publishes.

result is CHECK_DIGIT_VALID, CHECK_DIGIT_INVALID or MALFORMED. Only spaces are removed; any other character is MALFORMED, never cleaned up. A valid check digit proves neither ABR nor GST registration, that the number was issued or that it is active: retain not_established and use ABN Lookup for those. Reads no network.

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": "validate_abn"
  }
}

Input Schema

NameRequiredDescriptionDefault
abnYesThe ABN as written: 11 digits, optionally separated by spaces.

Output Schema

NameRequiredDescriptionDefault
okYesThe check ran; not that the number passed.
reasonYes
resultYesOutcome of the arithmetic; never a registration status.
formattedYesThe digits in the usual groups; null when malformed.
identifierYes
source_urlYes
source_checkedYesDate in YYYY-MM-DD form.
not_establishedYesRetain when presenting the result.
source_provisionYes
check_digit_validYes
abr_registration_establishedYesA check digit never establishes ABR registration.
gst_registration_establishedYesA check digit never establishes GST registration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.23

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: the three-way result taxonomy, the rule that only spaces are stripped and any other character yields MALFORMED without cleanup, and confirmation that no network is read. The lack of pagination/return-shape discussion is minor given an output schema exists, but the added context is meaningful rather than essential.

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-loads the purpose, then the result enum, then the normalization rule, then the caveat and fallback. Every sentence carries distinct information and nothing is restated from the schema or annotations.

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?

A single-parameter, deterministic validator with annotations, an output schema and 100% schema coverage. The description covers purpose, result values, input normalization, and the interpretive limits of a valid result, leaving nothing an agent needs before calling it.

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 coverage is 100% and the schema already describes the abn field as 11 digits optionally space-separated, so the baseline is met. The description then adds meaning the schema does not: normalization behavior (spaces stripped, nothing else cleaned) which is exactly what an agent needs to predict MALFORMED outcomes.

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 precise verb and resource ("Test an ABN against the check digit arithmetic") and immediately narrows the scope to check-digit arithmetic only, distinguishing it from registration lookups and implicitly from validate_acn/validate_bsb_format siblings that operate on other identifier types.

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 what the result does NOT establish (ABR or GST registration, issuance, active status) and redirects to ABN Lookup for those, plus "retain not_established" tells the agent how to handle the gap. It never names the sibling validators (validate_acn, validate_bsb_format), so the alternative-selection guidance is partial rather than exhaustive.

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