Skip to main content
Glama
Australian Accounting MCP

Australian Accounting MCP

Test a BSB's format

validate_bsb_format
Read-onlyIdempotent

Validate an Australian BSB against AusPayNet BECS formatting (6 digits, XXX-XXX) and return FORMAT_VALID or MALFORMED; this checks structure only, not whether the BSB exists.

Instructions

Test a BSB against the format AusPayNet's BECS Procedures publish: 6 digits, XXX-XXX.

result is FORMAT_VALID or MALFORMED. Spaces and one hyphen after the third digit are removed; any other character is MALFORMED, never cleaned up. A BSB has no check digit and this server holds no BSB directory, so a valid format proves neither that AusPayNet issued the BSB nor that it exists or accepts payments: retain not_established and use AusPayNet's BSB 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": {
      "bsb": "<bsb>"
    },
    "name": "validate_bsb_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
bsbYesThe BSB as written: 6 digits as XXX-XXX or without the hyphen, optionally separated by spaces.

Output Schema

NameRequiredDescriptionDefault
okYesThe check ran; not that the BSB exists.
reasonYes
resultYesOutcome of the format test; never a directory lookup.
formattedYesThe BSB as XXX-XXX; null when malformed.
identifierYes
source_urlYes
source_checkedYesDate in YYYY-MM-DD form.
not_establishedYesRetain when presenting the result.
source_provisionYes
institution_establishedYesA format test never establishes that AusPayNet issued the BSB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.23

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds behavior those annotations cannot convey: spaces and one hyphen after the third digit are stripped, any other character is MALFORMED and never repaired, and the tool performs no check-digit or directory verification. 'Reads no network' reinforces the closed-world hint with concrete meaning.

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-loaded with the format rule, then the outcome vocabulary, then the normalization rules and limitations. Dense but every sentence carries information; the trailing 'Reads no network.' fragment is slightly abrupt and could be merged into the preceding limitation sentence.

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 tool with a full schema and an output schema, the description supplies exactly the missing context: the format standard, the two result outcomes, the normalization policy, and the scope limits on what a pass means. Nothing needed to call it correctly is absent.

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%, so baseline is 3, but the description earns more by documenting the normalization preconditions the schema only hints at: which separators are tolerated and that the input is never silently cleaned beyond that. It does not restate the maxLength or type, which the schema already owns.

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 ('a BSB') along with the exact external standard it validates against (AusPayNet BECS: 6 digits, XXX-XXX). The resource is clearly distinct from sibling validators (ABN, ACN, account number), so an agent can select it without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly bounds the tool: a valid format proves neither issuance nor existence nor payment acceptance, and the agent is told to retain 'not_established' and route existence questions to AusPayNet's BSB Lookup. This is a clear when-to-use/when-not-to-use split with a named alternative.

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