Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_s_corp_reasonable_salary

Calculate S-Corp FICA tax savings by comparing net business profit, reasonable W-2 salary, and compliance costs to determine shareholder distributions and election viability.

Instructions

S-Corporation Reasonable Salary & Tax Savings Calculator. Calculate annual FICA self-employment tax savings from electing S-Corp status, optimizing reasonable compensation salary versus shareholder distributions. Discipline: FINANCE. Governing mathematical model / formula: FICA Savings = (Net Business Profit - Reasonable Salary) × 15.3%.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of net_annual_tax_savings (Net Annual Cash Tax Savings), shareholder_distribution (FICA-Free Shareholder Distributions), gross_fica_savings (Gross FICA Self-Employment Tax Saved), s_corp_threshold_rating (S-Corp Viability Verdict) using net_business_profit (Annual Net Business Profit), reasonable_salary_target (Justifiable Reasonable W-2 Salary), corporate_compliance_costs (Annual Payroll & CPA Filing Fees). 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 'S-Corporation Reasonable Salary & Tax Savings 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): "s-corp-reasonable-salary"

    • category (string): "finance"

    • name (string): "S-Corporation Reasonable Salary & Tax Savings Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.net_annual_tax_savings (Net Annual Cash Tax Savings): Formatted display string (e.g. '$11,570.00 / yr')

      • metrics.shareholder_distribution (FICA-Free Shareholder Distributions): Formatted display string (e.g. '$90,000.00')

      • metrics.gross_fica_savings (Gross FICA Self-Employment Tax Saved): Formatted display string (e.g. '$13,770.00 / yr')

      • metrics.s_corp_threshold_rating (S-Corp Viability Verdict): Formatted display string (e.g. 'Highly Profitable Election (Saves > $5k/yr)')

    • 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_s_corp_reasonable_salary"
  }
}

Input Schema

NameRequiredDescriptionDefault
net_business_profitNoAnnual Net Business Profit. Gross revenue minus all operating expenses. Default: 160000. Min: 30000. Max: 2000000.
reasonable_salary_targetNoJustifiable Reasonable W-2 Salary. Defensible salary for your role under IRS standards. Default: 70000. Min: 20000. Max: 500000.
corporate_compliance_costsNoAnnual Payroll & CPA Filing Fees. Gusto/ADP payroll + Form 1120-S corporate tax return. Default: 2200. Min: 500. Max: 10000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares the tool read-only, idempotent, stateless, and free of side effects, and it explains that out-of-bounds inputs return a safe diagnostic error rather than throwing. That covers safety profile, failure mode, and determinism beyond what any structured field provides.

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?

Sectioned with headers and front-loaded with the purpose and formula, so an agent can stop reading early if it already knows the tool fits. It is somewhat long, and the parameter-name restatements plus the verbose RETURNS listing repeat information, but no section is truly wasted.

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?

For a three-parameter deterministic calculator with no output schema, the description supplies everything needed: input semantics, formula, error behavior, and a full enumeration of the returned fields including the metrics object. Nothing an agent needs in order to call it correctly or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning by giving the formula 'FICA Savings = (Net Business Profit - Reasonable Salary) × 15.3%', which shows how the three parameters combine and why compliance costs erode the net figure. The restated parameter labels largely duplicate the schema.

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 verb and resource ('Calculate annual FICA self-employment tax savings from electing S-Corp status') and even supplies the governing formula, so the tool's function is unambiguous. It explicitly distinguishes itself from generic dispatchers (omni_universal_query) and from omni_batch_calculate and omni_describe_solver.

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?

Explicit WHEN TO USE and WHEN NOT TO USE blocks state the exact outputs computed and the three required inputs, and the exclusion ('Do not use for qualitative evaluations or unquantified reasoning') is concrete. Alternatives for chained jobs (omni_batch_calculate) and schema inspection (omni_describe_solver) are named with the condition that selects them.

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