Skip to main content
Glama

BRAINIAC Bank Account Identifiers & Payment Files

Validate or generate a UETR

bank-payments_uetr-validate
Read-onlyIdempotent

Validate an ISO 20022 UETR as a UUID version 4, or generate one or more UETRs with crypto.randomUUID(). Price $0.01 USDC. POST /api/v1/bank-payments/uetr-validate. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bank-payments_uetr-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
uetrNouetr, string, length 1 to 64. Optional.
countNocount, integer, from 1 to 100. Optional.
generateNogenerate, boolean. Optional.

Output Schema

NameRequiredDescriptionDefault
uetrNouetr. String.
validNovalid. Boolean.
reasonNoreason. Null.
sourcesNosources. Array.
variantNovariant. String.
versionNoversion. Number.
normalisedNonormalised. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds meaningful behavior beyond the annotations: the POST path, a $0.01 USDC price, and critically that an unpaid call returns x402 payment terms and does not execute. That payment-gating detail is exactly the kind of context annotations cannot express. It stops short of covering defaults or the count/generate interaction.

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?

A single tight paragraph with the core purpose front-loaded, followed by the cost and endpoint, then the failure mode. Every sentence carries information; the raw route string is slightly technical filler but still useful to an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers both branches plus the payment failure path. The remaining gap is the parameter interaction (does 'generate' default to false, and what if a uetr is passed alongside generate=true), which matters for correct invocation.

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%, so the baseline is 3 despite the schema's descriptions being generic boilerplate. The description adds real semantics by tying 'uetr' to UUID v4 validation and 'count' to how many UETRs are generated, but it never says which parameters are relevant to which mode.

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 two specific operations—validating an ISO 20022 UETR as a UUID v4, and generating one or more UETRs via crypto.randomUUID()—with concrete format detail. No sibling tool covers UETR handling, so the resource alone distinguishes it from the other validate/parse tools in the family.

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

Usage Guidelines3/5

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

The description implies the two modes (validate vs. generate) but never states the selection rule explicitly, nor what happens if both 'uetr' and 'generate' are supplied. There is no when-not-use guidance or pointer to any alternative tool, leaving the agent to infer that 'generate=true' selects the generation path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources