Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_social_security_taxation

Calculate the taxable portion of Social Security benefits and provisional combined income by filing status, determining the 0%, 50%, or 85% federal tax tier.

Instructions

Social Security Benefits Taxation Calculator. Calculate how much of your Social Security retirement benefit is subject to federal income tax (0%, 50%, or 85%) based on provisional combined income. Discipline: FINANCE. Governing mathematical model / formula: Provisional Income = AGI (Excluding SS) + Non-Taxable Interest + (50% of Social Security).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of taxable_social_security_amount (Taxable Social Security Income), provisional_combined_income (Provisional Combined Income), tax_free_benefit_share (100% Tax-Free Benefit Share), tax_tier_category (Social Security Tax Bracket Tier) using annual_social_security_benefit (Annual Social Security Benefits Received), other_taxable_income (Other Income (Pensions, 401k, Dividends, W-2)), tax_exempt_municipal_interest (Tax-Exempt Municipal Bond Interest), filing_status_ss (Tax Filing Status (1 = Single, 2 = Married Filing Jointly)). 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 'Social Security Benefits Taxation 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): "social-security-taxation"

    • category (string): "finance"

    • name (string): "Social Security Benefits Taxation Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.taxable_social_security_amount (Taxable Social Security Income): Formatted display string (e.g. '$23,700.00 (74.1%)')

      • metrics.provisional_combined_income (Provisional Combined Income): Formatted display string (e.g. '$61,000.00')

      • metrics.tax_free_benefit_share (100% Tax-Free Benefit Share): Formatted display string (e.g. '$8,300.00 (25.9% Tax-Free)')

      • metrics.tax_tier_category (Social Security Tax Bracket Tier): Formatted display string (e.g. 'Tier 2 (Up to 85% Taxable)')

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

Input Schema

NameRequiredDescriptionDefault
filing_status_ssNoTax Filing Status (1 = Single, 2 = Married Filing Jointly). Single: $25k-$34k (50%), >$34k (85%); MFJ: $32k-$44k (50%), >$44k (85%). Default: 2. Min: 1. Max: 2.
other_taxable_incomeNoOther Income (Pensions, 401k, Dividends, W-2). All ordinary income, pensions, and RMDs. Default: 45000. Min: 0. Max: 500000.
tax_exempt_municipal_interestNoTax-Exempt Municipal Bond Interest. Muni interest is counted in combined income. Default: 0. Min: 0. Max: 100000.
annual_social_security_benefitNoAnnual Social Security Benefits Received. Gross benefit on Form SSA-1099 box 5. Default: 32000. Min: 5000. Max: 100000.

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 behavioral burden and does so thoroughly: it declares pure deterministic computation, machine floating-point precision, read-only/idempotent/stateless behavior, zero side effects, input validation against bounds, and safe diagnostic errors instead of runtime exceptions. It also documents the exact return structure, which is critical since no output schema exists.

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?

The description is front-loaded with purpose and formula, then organized into clear usage, disambiguation, behavior, and returns sections. It is somewhat long, especially the detailed RETURNS enumeration, but that detail is justified because no output schema exists and the structure remains easy to scan.

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 four-parameter deterministic calculator with no annotations and no output schema, the description covers purpose, formula, usage boundaries, input meanings, safety behavior, validation, and return fields. An agent has enough information to call the tool correctly and interpret its response without opening additional resources.

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%, and the schema already documents each parameter with defaults, bounds, and filing-status threshold details. The description restates the parameter meanings in the usage section and provides the governing formula, but it adds little parameter-level detail beyond what the schema already supplies, so the baseline of 3 is appropriate.

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 opens with a specific tool title and immediately states the exact calculation: how much Social Security retirement benefit is subject to federal income tax at 0%, 50%, or 85% based on provisional combined income. It names the governing formula and distinguishes the tool from generic dispatchers like omni_universal_query.

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 gives explicit WHEN TO USE and WHEN NOT TO USE sections, lists the exact outputs and inputs, and includes disambiguation guidance for generic dispatchers, batch calculations via omni_batch_calculate, and schema inspection via omni_describe_solver. This leaves little ambiguity about when to select this tool versus alternatives.

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