Skip to main content
Glama

ErisaLedger US 401(k) SECURE 2.0

erisaledger_evaluate_state_auto_ira

Evaluates US State Auto-IRA statutory compliance mandates and per-employee penalty exposure across 15 active state programs.

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": {
      "state_code": "<state_code>",
      "employee_count": "<employee_count>"
    },
    "name": "erisaledger_evaluate_state_auto_ira"
  }
}

Input Schema

NameRequiredDescriptionDefault
state_codeYes
employee_countYes
has_qualified_planNo

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 behavioral burden. It reveals the scope (15 active state programs) and the output concept (penalty exposure), but says nothing about whether this is read-only, how unsupported state codes are handled, whether it lists the 15 states, or what the response contains. Significant gaps remain for a mutation-free but non-trivial compliance evaluator.

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 tightly written sentence with the resource and scope front-loaded and no filler. Appropriately sized, though brevity here is partly the source of the missing-guidance gaps elsewhere.

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 compliance-and-penalty evaluator with 3 undocumented parameters, no annotations, and no output schema, one sentence is not enough. An agent lacks the state-code domain, the meaning of has_qualified_plan, and any expectation of the returned structure.

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 three parameters. The description hints that employee_count drives 'per-employee penalty exposure,' but it never defines state_code format, the 15 valid programs, or what has_qualified_plan=true/false changes in the evaluation (crucial given its default of false). The description does not compensate for the documentation gap.

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 ('Evaluates') and a well-defined resource (US State Auto-IRA statutory compliance mandates and per-employee penalty exposure across 15 active state programs). This clearly separates it from sibling calculators like form 8881 credit and VFCP late deposits. It stops short of explicitly naming a sibling alternative, so a 4 rather than 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 guidance, no prerequisites, and no named alternatives. The compliance-evaluation framing implies a context but does not tell an agent when to choose this tool over the sibling audit or calculation tools.

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.