achlens
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACHLENS_ALLOWED_ROOTS | No | Configure ACHLENS_ALLOWED_ROOTS to enable MCP path inputs; otherwise provide file content directly. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_statusA | Return the local achlens server status. |
| validate_ach_fileC | Validate an ACH file and return structured findings and aggregate counts. |
| summarize_ach_fileC | Summarize ACH structure, totals, SEC codes, returns, and NOCs. |
| parse_ach_fileC | Parse named ACH fields in a bounded page of records. |
| explain_control_totalsC | Explain stated versus recomputed batch and file control totals. |
| check_routing_numberB | Check an ABA routing number's mathematical check digit. |
| lookup_ach_codeC | Look up a return, NOC, transaction, SEC, or service-class code. |
| generate_test_ach_fileA | Generate a balanced synthetic ACH file for testing, never transmission. |
| repair_control_records_toolC | Repair derived controls, returning content only in content mode. |
| diff_ach_files_toolB | Compare two ACH contents and return masked field-level differences. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| debug_ach_file | Guide deterministic ACH validation and control-total debugging. |
| explain_returns | Guide a concise returns and NOCs explanation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| layouts | The packaged ACH record layouts. |
| rules | The packaged ACH validation rule catalog. |
TDQS
Scored across 10 tools
Each tool targets a distinct action or resource (validate, summarize, parse, explain, repair, diff, generate, lookup, check, status). Slight overlap exists between validate_ach_file, summarize_ach_file, and explain_control_totals regarding control totals, but their outputs and purposes are clearly differentiated by description.
Most names follow a consistent verb_noun snake_case pattern (e.g., validate_ach_file, parse_ach_file, check_routing_number). Two tools break this with a '_tool' suffix (repair_control_records_tool, diff_ach_files_tool), and server_status uses a noun_noun form, but overall the set is predictable.
10 tools is well within the ideal range for this domain. Each tool addresses a specific need—validation, parsing, summarization, code lookup, generation, repair, diff, and status—without redundancy or bloat.
The surface covers core ACH file operations: validation, parsing, summarization, control total explanation, code lookup, routing checks, test file generation, control repair, and diffing. Minor gaps exist for broader file editing or production file creation, but these may be outside the intended scope.