Skip to main content
Glama

ErisaLedger US 401(k) SECURE 2.0

erisaledger_calculate_vfcp_late_deposit

Computes DOL Voluntary Fiduciary Correction Program (VFCP) lost earnings at IRC Sec. 6621 underpayment interest rates and IRC Sec. 4975 excise tax avoided on late participant deferral deposits.

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": {
      "payroll_remittances": "<payroll_remittances>"
    },
    "name": "erisaledger_calculate_vfcp_late_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearNo
payroll_remittancesYes
safe_harbor_business_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It names the regulatory basis (Sec. 6621 rates, Sec. 4975 excise tax), which is genuinely useful context for interpreting the number, but says nothing about rate-table selection by tax year, the VFCP correction assumptions applied, the precision/rounding, or whether the result is advisory only. For a financial calculation tool with no output schema, return-value behavior is entirely undocumented.

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 front-loaded sentence starting with the verb and immediately naming the program and computation. It is dense with regulatory jargon but every clause adds a distinct piece of meaning. Nothing is padded or repeated.

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?

The tool is complex — a regulatory financial calculation with a nested required array parameter, no annotations, and no output schema — yet the description supplies only the purpose and legal citations. An agent lacks what it needs to construct payroll_remittances correctly or interpret the computed result, which is a substantial gap at this complexity level.

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?

All three parameters have 0% schema description coverage, and the description names none of them. 'Late participant deferral deposits' faintly implies what payroll_remittances holds, but the required parameter is an untyped array of objects with no guidance on element shape, and safe_harbor_business_days (a term of art tied to VFCP safe-harbor deposit timing) and the tax_year rate-table selector are left completely unexplained.

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 gives a specific verb ('Computes') and a precise, technical resource: VFCP lost earnings under IRC Sec. 6621 rates plus Sec. 4975 excise tax avoided on late participant deferral deposits. An agent knows exactly what result this produces. It stops short of 5 because it never contrasts itself with siblings such as erisaledger_calculate_form_8881_credit, though the highly specific domain phrasing makes confusion unlikely.

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 or when-not-to-use guidance, no trigger conditions, and no routing to alternatives (e.g., when to use the Form 8881 credit calculator instead). The phrase 'on late participant deferral deposits' is the only implicit signal of the applicable scenario. Prerequisites such as who may file under VFCP are absent.

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.