Skip to main content
Glama
Sign In
achlens

achlens

by mscott9160-web
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_routing_number

Validates an ABA routing number's check digit to detect mistyped or invalid numbers before ACH processing.

Instructions

Check an ABA routing number's mathematical check digit.

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": {
      "routing_number": "<routing_number>"
    },
    "name": "check_routing_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
routing_numberYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose an important behavioral limit by specifying the check is mathematical (checksum only, not registry lookup), which is real value. However, it says nothing about permissions, error behavior, or what an invalid input yields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero filler, and the scope qualifier is placed front and center. Nothing is wasted.

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

Completeness3/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-value explanation is not required. Still, for a tool whose whole purpose is a binary check, the description never says what the check implies (e.g., checksum validity vs. account existence) or the input format, leaving modest gaps.

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?

With 0% schema description coverage on a single parameter, the description must compensate. Calling it an 'ABA routing number' implies the domain and expected identifier type, but it omits the 9-digit format and whether separators are accepted, leaving a gap the schema does not fill.

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 states a specific verb (Check) and resource (ABA routing number) and narrows the scope to the mathematical check digit, which cleanly separates it from siblings like validate_ach_file or parse_ach_file. It does not name a sibling explicitly, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The narrow scope implies this is a format-level check rather than full account validation, but the agent must infer that from 'check digit' alone, which is thin.

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

Deploy Server

Other Tools