Skip to main content
Glama
Australian Accounting MCP

Australian Accounting MCP

Test an ACN check digit

validate_acn
Read-onlyIdempotent

Validate an Australian Company Number using ASIC's check digit arithmetic, returning CHECK_DIGIT_VALID, CHECK_DIGIT_INVALID, or MALFORMED to catch input errors before relying on the ACN.

Instructions

Test an ACN against the check digit arithmetic ASIC 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 ASIC issued the number or that a company holds it: retain not_established and search ASIC's registers and 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": {
      "acn": "<acn>"
    },
    "name": "validate_acn"
  }
}

Input Schema

NameRequiredDescriptionDefault
acnYesThe ACN as written: 9 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.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the normalization rule (only spaces stripped, every other character yields MALFORMED and is never silently cleaned), the three possible result states, and the explicit epistemic limit of a valid result. 'Reads no network' reinforces openWorldHint=false with a plain-language statement an agent can rely on.

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 core action in the first sentence, then enumerates result states, then the caveat. Every clause carries distinct information; nothing restates the name or schema.

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, non-destructive, offline check with an output schema and full annotation coverage is fully described: input normalization, output enumerations, and the limits of interpretation are all stated. Nothing an agent needs in order to call it correctly is missing.

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 acn property already documents the 9-digit/optional-spaces format, so the baseline is met without effort. The description still adds genuine meaning the schema lacks: whitespace is the only tolerated separator and malformed input is reported rather than repaired, which tells the agent not to pre-sanitize input.

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 (test) and resource (ACN) plus the exact algorithm class: ASIC's published check-digit arithmetic. Ambiguity with the sibling validate_abn is avoided by naming the resource domain (ACN, a 9-digit company number) and by spelling out that a pass proves nothing about ABR/GST registration.

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 a clear when-not-to-use path: a valid check digit establishes nothing about registration or company existence, and the description routes those questions to ASIC's registers and ABN Lookup. It does not name a specific sibling tool as the alternative, but it names the correct external source, which is sufficient for routing.

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