Skip to main content
Glama

FinOps Studio Zero-Auth Bank Validator & 2-Row Taste-Test MCP

preview_us_nacha_ach_2_rows

Free 2-row taste-test preview of 94-character Block-10 padded US NACHA ACH (.ach) files with ABA MOD-10 verification.

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": {
      "immediateDestination": "<immediateDestination>",
      "companyName": "<companyName>",
      "companyId": "<companyId>",
      "entries": "<entries>"
    },
    "name": "preview_us_nacha_ach_2_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYes
secCodeNoCCD
companyIdYes
companyNameYes
immediateDestinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two useful traits: output is fixed-width 94-character Block-10 padded and ABA check-digit (MOD-10) verification is applied, and that the result is truncated to 2 rows. It omits whether files are written to disk or returned inline, authentication/API-key requirements, rate or cost limits after the free tier, and failure behavior for invalid routing numbers.

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 dense sentence that front-loads the key qualifiers (free, 2-row, taste-test, format). Nothing is redundant, though the marketing-flavored 'taste-test' phrasing consumes space that could have documented the required routing and company identifiers.

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

Completeness2/5

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

For a five-parameter tool with no annotations, no output schema, and zero schema description coverage, the description is thin: an agent knows what format is produced but not what to supply for immediateDestination, companyId, companyName, or the entries objects, nor what the response looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, four of them required, so the description must compensate and largely does not. The only hint is 'ABA MOD-10 verification', which implies immediateDestination is a routing number carrying a check digit; companyId, companyName, secCode (default CCD), and the entries array structure remain entirely unexplained in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: a 2-row preview of US NACHA ACH (.ach) files, plus format details (94-character Block-10 padding, ABA MOD-10 verification). It clearly distinguishes the output format from the sibling preview tools (DATEV CSV, SEPA XML, BAI2, EU e-invoice), though it does not explicitly name any of them.

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?

'Taste-test preview' and 'free 2-row' imply this is a trial/evaluation call rather than production file generation, which is useful implicit guidance. However, there is no explicit statement of when to use this versus a full generation/validation tool, no preconditions, and no note on what happens beyond two rows.

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.