Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_section_179_deduction

Calculate Section 179 first-year equipment expensing deductions, phase-out status, immediate tax savings, and net equipment cost from purchase total, tax bracket, and net income.

Instructions

Section 179 Equipment Depreciation Calculator. Calculate immediate first-year Section 179 equipment expensing deductions ($1,220,000 limit in 2024), phase-out ceilings, and net equipment acquisition cost. Discipline: FINANCE. Governing mathematical model / formula: Section 179 Deduction = min(Equipment Cost, $1,220,000) | Net Equipment Cost = Purchase Price - Cash Tax Saved.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of section_179_deduction_amount (Year 1 Section 179 Tax Deduction), immediate_cash_tax_savings (Direct Cash Tax Savings), net_effective_equipment_cost (True Out-of-Pocket Equipment Cost), phaseout_status_indicator (Phase-Out Threshold Status ($3,050,000)) using equipment_purchase_total (Total Qualifying Equipment Purchased), business_tax_bracket_pct (Business / Owner Marginal Tax Rate (%) in %), annual_business_net_income (Annual Business Taxable Net Income). 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Section 179 Equipment Depreciation Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

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): "section-179-deduction"

    • category (string): "finance"

    • name (string): "Section 179 Equipment Depreciation Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.section_179_deduction_amount (Year 1 Section 179 Tax Deduction): Formatted display string (e.g. '$240,000.00')

      • metrics.immediate_cash_tax_savings (Direct Cash Tax Savings): Formatted display string (e.g. '$84,000.00 Cash Saved')

      • metrics.net_effective_equipment_cost (True Out-of-Pocket Equipment Cost): Formatted display string (e.g. '$156,000.00 (35% Effective Discount)')

      • metrics.phaseout_status_indicator (Phase-Out Threshold Status ($3,050,000)): Formatted display string (e.g. 'Full Deduction (Below Phase-Out Ceiling)')

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

Input Schema

NameRequiredDescriptionDefault
business_tax_bracket_pctNoBusiness / Owner Marginal Tax Rate (%) (%). Federal + state marginal tax bracket. Default: 35. Min: 10. Max: 45.
equipment_purchase_totalNoTotal Qualifying Equipment Purchased. Machinery, computers, heavy vehicles > 6,000 lbs, software. Default: 240000. Min: 5000. Max: 5000000.
annual_business_net_incomeNoAnnual Business Taxable Net Income. Section 179 cannot exceed net business taxable income. Default: 450000. Min: 10000. Max: 10000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/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 side-effect free, and states that out-of-bounds inputs return a safe diagnostic error instead of throwing. That is precisely the behavioral context an agent needs before calling a calculator with bounded inputs.

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?

Content is front-loaded with the tool's identity and formula, and each section (usage, behavior, returns) is labeled and scannable. Some redundancy exists between the formula line and the usage-guidelines restatement of parameters, but no section is padded with meaningless prose.

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?

There is no output schema and no annotations, but the description compensates by enumerating every returned field (status, calculator, category, formula, inputs, metrics with all four computed outputs) and each metric's meaning and format. For a three-parameter deterministic calculator, nothing an agent needs is missing.

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 three parameters (equipment purchase total, marginal bracket %, net business income) are already fully documented in the schema. The description names them and adds the useful note that Section 179 cannot exceed net business taxable income, but otherwise restates rather than expands schema content, so the baseline 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?

States a specific verb and resource ('Section 179 Equipment Depreciation Calculator') and gives the governing formula (min(Equipment Cost, $1,220,000)), so the agent knows exactly what computation happens. It also explicitly contrasts itself with omni_universal_query, making sibling differentiation possible 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?

Has explicit WHEN TO USE naming every output metric and input, a WHEN NOT TO USE clause excluding qualitative/unquantified reasoning, and SIBLING ROUTING that points to omni_universal_query for cross-discipline dispatch. The selection conditions are stated rather than inferred.

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