Skip to main content
Glama

ErisaLedger US 401(k) SECURE 2.0

erisaledger_audit_secure2_census

Audits anonymized participant census records for 2026 SECURE 2.0 Sec. 603 mandatory Roth catch-up violations (>$150k prior FICA wages), Sec. 125 500-hour Long-Term Part-Time eligibility omissions, and 402(g)/415(c)/Super Catch-Up limits.

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": {
      "employees": "<employees>"
    },
    "name": "erisaledger_audit_secure2_census"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearNo
employeesYes
state_codeNoCA
plan_start_yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 behavioral burden. It discloses useful domain behavior by naming the specific SECURE 2.0 checks and thresholds, but it does not state whether the audit is read-only, what permissions or anonymization assumptions apply, whether records are modified, or what the result contains.

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?

The description is a single, front-loaded sentence with no filler. The enumerated compliance areas and thresholds earn their place by specifying the audit scope precisely.

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 tool with four parameters, a nested employees array, no annotations, no output schema, and 0% schema coverage, the description is incomplete. It is strong for selection but omits parameter details and return/result information needed for correct invocation.

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%, so the description must compensate for all four parameters. It only hints that employees are census records and that the relevant year is 2026; it does not explain the employee object fields, state_code, or plan_start_year, leaving most parameter meaning undocumented.

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

Purpose5/5

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

States the specific verb 'Audits' and resource 'anonymized participant census records,' then enumerates three compliance check areas with thresholds. This is clearly distinguishable from the sibling calculation and evaluation tools, which do not audit census records.

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?

The description implies usage by naming the compliance areas being audited, but it does not explicitly state when to use this tool versus sibling calculators or when not to use it. No prerequisites, exclusions, or alternatives are given.

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.