Skip to main content
Glama

US Tax Estimator

Compare catch-up options for unreported foreign assets

compare_offshore_compliance_options
Read-onlyIdempotent

For a U.S. taxpayer who missed FBAR or Form 8938 filings or left foreign income unreported, estimates and compares the cost of three catch-up paths: A) delinquent information return procedures (only when no income went unreported), B) amended returns with tax and interest plus a reasonable-cause statement (with the statutory penalty exposure if reasonable cause is rejected), and C) the Streamlined Domestic Offshore Procedures (tax, interest and the 5% penalty). Also adds the 1% Form 720 excise tax on premiums paid to foreign insurers. Tax years 2019–2025. Assumes non-willful conduct; it does not decide eligibility.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filing_status": "<filing_status>",
      "years": "<years>"
    },
    "name": "compare_offshore_compliance_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsYesOne entry per affected tax year.
filing_statusYesFiling status used on the original returns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the modeling assumptions and boundaries: non-willful only, tax years 2019–2025, reasonable-cause rejection risk included, and an explicit disclaimer that eligibility is not determined. It stops short of noting precision/rounding caveats on the estimates.

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?

One dense but well-ordered paragraph: it front-loads the taxpayer scenario and the three options, then adds the excise add-on and year/assumption caveats. Every clause carries information, though the option list could be scanned more easily if broken out.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does so by naming the three cost comparisons and the add-on excise. Scope (years) and assumptions (non-willful) are stated, leaving only minor gaps like result formatting or whether both paths are always returned.

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% and self-documenting, so the baseline is 3, but the description adds meaningful semantics by tying inputs to outputs – premiums drive the 1% Form 720 excise, unreported asset values drive the Streamlined 5% penalty, and path B includes statutory penalty exposure. This helps an agent understand why those fields matter.

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 ('estimates and compares the cost of three catch-up paths') and then enumerates exactly what each path computes (A delinquent procedures, B amended returns with reasonable cause, C Streamlined Domestic). This is clearly distinguishable from siblings like estimate_federal_tax or screen_foreign_life_insurance_7702.

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?

Gives real eligibility context: option A applies 'only when no income went unreported', the whole model 'assumes non-willful conduct', and it explicitly says it 'does not decide eligibility'. It doesn't name sibling tools or say when a different tool is the better first call, so it lands just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources