Skip to main content
Glama
tresor4k

macalc

calculate_us_401k

Calculate US 401(k) retirement savings: employee contribution, employer match, and total annual amount. Input salary, contribution percentage, employer match terms, and age to determine catch-up eligibility and contribution limits.

Instructions

Calculate US 401(k) contribution, employer match, and total retirement savings. Returns: {annual_salary, employee_contribution, employer_match, total_annual_contribution, catch_up_eligible, max_employee_limit}. See list_bundles for related 'finance-us' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annual_salaryYesAnnual salary in USD
contribution_pctYesEmployee contribution percentage (1-100)
employer_match_pctNoEmployer match percentage of employee contribution (default 50%)
employer_match_limitNoEmployer match cap as % of salary (default 6%)
ageNoEmployee age (50+ enables catch-up contributions)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior4/5

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

With no annotations, the description discloses the tool calculates and returns specific fields, implying a read-only, non-destructive operation. It provides sufficient behavioral context for a calculator.

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 two sentences: the first stating the purpose, the second listing return fields and referencing related tools. It is front-loaded and concise with no wasted words.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a calculator with a complete schema and implied output schema via the description, the description covers purpose and return fields. It could mention age's effect on catch-up contributions but is otherwise sufficient.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no additional parameter context beyond listing return fields, meeting the baseline for high coverage.

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?

The description clearly states the tool calculates US 401(k) contributions, employer match, and total retirement savings, listing specific return fields. It distinguishes itself from siblings by directing users to list_bundles for related 'finance-us' calculators.

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

Usage Guidelines4/5

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

The description implicitly indicates usage for 401k calculations and suggests list_bundles for related tools, but does not explicitly state when to use this tool versus alternatives or provide exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server