Skip to main content
Glama
Australian Accounting MCP

Australian Accounting MCP

Test a bank account number's format

validate_account_number_format
Read-onlyIdempotent

Validates an Australian bank account number against AusPayNet BECS formatting rules, returning FORMAT_VALID or MALFORMED without confirming the account exists.

Instructions

Test an account number against the account number field in AusPayNet's BECS Procedures.

result is FORMAT_VALID or MALFORMED. The field takes up to 9 ASCII letters, digits, hyphens or spaces, not all zeros or blanks; hyphens are removed from a longer number, as the procedures direct, and spaces at either end are removed. Any other character is MALFORMED, never cleaned up. The procedures set no check digit and this server holds no account data, so a valid format proves neither that the account exists or belongs to the payee nor that it matches a BSB: retain not_established. 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": {
      "account_number": "<account_number>"
    },
    "name": "validate_account_number_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_numberYesThe Australian bank account number as written, without the BSB.

Output Schema

NameRequiredDescriptionDefault
okYesThe check ran; not that the account exists.
reasonYes
resultYesOutcome of the format test; never an account lookup.
formattedYesThe account number as the BECS field carries it, without its blank fill; null when malformed.
identifierYes
source_urlYes
source_checkedYesDate in YYYY-MM-DD form.
not_establishedYesRetain when presenting the result.
source_provisionYes
account_establishedYesA format test never establishes that the account exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.23

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the exact normalization rules (hyphens stripped from longer numbers, leading/trailing spaces trimmed, other characters never cleaned), the accepted alphabet and length limit, the no-check-digit policy, and 'Reads no network.' The annotations already cover read-only/idempotent/no-destructive, and the description adds the substantive behavioral detail.

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-loads the purpose and the outcome tokens, then the rules, then the caveats — a logical order with no filler sentences. It is dense and slightly run-on ('proves neither that the account exists or belongs to the payee nor that it matches a BSB'), which costs a point on readability but not on substance.

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 format validator with an output schema, the description supplies everything needed: what is validated, the normalization rules, both possible results, and the limits of what a pass means. Nothing an agent needs in order to call it or interpret 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 schema documents the single parameter, so the baseline is already met; the description still adds real meaning by specifying the effective 9-character alphabet/limit versus the schema's maxLength of 40, and by clarifying that the BSB must not be included.

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 ('Test an account number against the account number field in AusPayNet's BECS Procedures') and scopes it precisely to format only. It explicitly rules out BSB matching and account existence, which separates it from validate_bsb_format and the other validators.

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 clear context for when the result is meaningful and warns that a valid format does not prove account existence, ownership, or BSB match, instructing the caller to retain not_established. It stops short of naming sibling validators to use instead for BSB or entity checks, so the routing guidance is implicit rather than explicit.

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