Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_fsa_use_it_or_lose_it

Calculate net FSA tax savings and optimal annual election to prevent forfeiture of unused healthcare funds under IRS use-it-or-lose-it rules.

Instructions

Healthcare FSA Contribution & Forfeiture Calculator. Calculate Healthcare Flexible Spending Account (FSA) tax savings, optimal annual election, and avoid forfeiture under the IRS 'use-it-or-lose-it' rule. Discipline: FINANCE. Governing mathematical model / formula: Net FSA Benefit = (FSA Contribution × Tax Rate %) - Forfeited Unused Balance.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of net_fsa_tax_savings (Net Cash Tax Savings Realized), forfeited_cash_loss (Estimated Forfeited Unused Cash), gross_tax_deduction_benefit (Gross Tax Deduction Value), fsa_recommendation (FSA Strategy Guidance) using annual_fsa_election (Annual Healthcare FSA Election (Max $3,200)), projected_medical_spend (Projected Out-of-Pocket Medical Expenses), marginal_tax_bracket_fsa (Combined Tax Bracket (Income + FICA) in %), employer_rollover_cap (Employer Plan Rollover Limit ($640 Max)). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Healthcare FSA Contribution & Forfeiture Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "fsa-use-it-or-lose-it"

    • category (string): "finance"

    • name (string): "Healthcare FSA Contribution & Forfeiture Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.net_fsa_tax_savings (Net Cash Tax Savings Realized): Formatted display string (e.g. '$696.30 Cash Saved')

      • metrics.forfeited_cash_loss (Estimated Forfeited Unused Cash): Formatted display string (e.g. '$0.00 (Protected by Rollover)')

      • metrics.gross_tax_deduction_benefit (Gross Tax Deduction Value): Formatted display string (e.g. '$791.25')

      • metrics.fsa_recommendation (FSA Strategy Guidance): Formatted display string (e.g. 'Optimal Election (Full Expenses Covered)')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_fsa_use_it_or_lose_it"
  }
}

Input Schema

NameRequiredDescriptionDefault
annual_fsa_electionNoAnnual Healthcare FSA Election (Max $3,200). 2024 IRS individual cap = $3,200. Default: 2500. Min: 250. Max: 3200.
employer_rollover_capNoEmployer Plan Rollover Limit ($640 Max). IRS allows up to $640 rollover into next plan year. Default: 640. Min: 0. Max: 640.
projected_medical_spendNoProjected Out-of-Pocket Medical Expenses. Copays, prescriptions, dental, vision, braces. Default: 2200. Min: 100. Max: 5000.
marginal_tax_bracket_fsaNoCombined Tax Bracket (Income + FICA) (%). 24% income tax + 7.65% FICA = 31.65%. Default: 31.65. Min: 15. Max: 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full behavioral burden and does so thoroughly: it declares the tool read-only, idempotent, stateless, deterministic, side-effect-free, and validation-safe with diagnostic error responses. It also describes the return envelope and output fields, which is important because there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and sectioned, but it is noticeably verbose for a four-parameter deterministic calculator. It repeats formulas, parameter bounds, and output field descriptions in multiple places, so several sentences do not add new value beyond the schema and returns section.

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

Completeness5/5

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

Given a deterministic calculator with no annotations and no output schema, the description supplies the missing behavioral, validation, and return-format context. It also covers alternatives and boundaries, leaving little an agent would need to infer before invoking the tool correctly.

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 defaults, bounds, and meanings for all four parameters. The description repeats parameter names and some bounds but does not add substantive interpretation beyond what the schema already provides, so the baseline of 3 applies.

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 names a specific calculator: Healthcare FSA contribution, tax savings, optimal election, and forfeiture under the use-it-or-lose-it rule. It also states the governing formula and distinguishes this tool from generic dispatchers and batch execution tools, so an agent can identify its exact purpose without opening the schema.

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

Usage Guidelines5/5

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

It provides explicit WHEN TO USE and WHEN NOT TO USE sections, including the exact calculation outputs, required input types, and the condition that all parameters must be numeric. It also names alternatives such as omni_universal_query, omni_batch_calculate, and omni_describe_solver, giving clear routing guidance.

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

Deploy Server

Other Tools