Skip to main content
Glama

ErisaLedger US 401(k) SECURE 2.0

erisaledger_calculate_form_8881_credit

Calculates deterministic IRS Form 8881 Part I (Startup & Contribution) and Part II (Auto-Enrollment) credits across a 5-year window, including retroactive IRC Sec. 6511 amended return recovery and 51-100 employee phase-outs.

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": {
      "total_employees_5k_plus": "<total_employees_5k_plus>",
      "nhce_count": "<nhce_count>",
      "eligible_startup_admin_costs": "<eligible_startup_admin_costs>",
      "employer_contributions_to_eligible_under_cap": "<employer_contributions_to_eligible_under_cap>",
      "plan_start_year": "<plan_start_year>"
    },
    "name": "erisaledger_calculate_form_8881_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nhce_countYes
audit_tax_yearNo
plan_start_yearYes
has_auto_enrollmentNo
total_employees_5k_plusYes
eligible_startup_admin_costsYes
employer_contributions_to_eligible_under_capYes

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 burden. 'Deterministic' hints at a pure, repeatable computation, and mention of retroactive amended return recovery implies historical years are handled, but nothing is said about whether this is read-only, what it returns, permissions, rounding, or what happens when the phase-out thresholds are exceeded.

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 with the primary purpose first and qualifiers trailing; no filler. It is dense with unexplained tax jargon (Sec. 6511, NHCE-adjacent phase-outs), which costs a bit of readability but nothing is wasted.

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?

A complex multi-part tax computation with 7 undocumented parameters, no annotations, and no output schema needs more than one sentence. Nothing is said about the shape of the result (e.g., per-year credit breakdown, Part I vs Part II totals), rounding, or the eligibility preconditions that gate the calculation.

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 7 parameters, so the description must compensate and largely does not. It hints at some mappings (the 5-year window implies the 5-element contributions array; phase-outs imply total_employees_5k_plus/nhce_count; Auto-Enrollment implies has_auto_enrollment), but units, array length expectations, the meaning of nhce_count, and the role of audit_tax_year vs plan_start_year are never explained.

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?

States a specific verb ('Calculates') and a specific resource (IRS Form 8881 Part I and Part II credits) and scopes it to a 5-year window with retroactive Sec. 6511 recovery and 51-100 employee phase-outs. This clearly separates it from the listed siblings (VFCP late deposits, Secure2 census, state auto-IRA), though it never explicitly names an alternative.

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?

No when-to-use guidance, no prerequisites (e.g., plan must be a new qualified plan, costs must be eligible), and no exclusions or pointers to alternatives. The only usage signal is implicit in the word 'Calculates'.

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.