Skip to main content
Glama

1031 or DST vs Opportunity Fund vs paying tax

compare_1031_qof_dst
Read-onlyIdempotent

Compares three uses of the same net sale proceeds over a holding period: pay the tax and reinvest, a 1031 exchange or DST rolling all proceeds, and an OZ 2.0 fund taking only the gain. Tax treatment only.

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": {
      "proceeds": "<proceeds>",
      "basis": "<basis>",
      "rate_now_pct": "<rate_now_pct>",
      "growth_pct": "<growth_pct>",
      "hold_years": "<hold_years>"
    },
    "name": "compare_1031_qof_dst"
  }
}

Input Schema

NameRequiredDescriptionDefault
basisYesAdjusted basis of the property sold
ruralNo
proceedsYesNet sale proceeds
growth_pctYes
hold_yearsYes
rate_now_pctYes
rate_later_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 bar is lower. The description adds real context beyond them by disclosing the comparison methodology (all proceeds vs gain only) and the 'Tax treatment only' limitation, which warns the agent that non-tax factors such as liquidity or depreciation are excluded.

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 front-loaded sentence that ends with the most important qualifier ('Tax treatment only'); nothing is wasted. The dense noun phrases make it slightly harder to scan than it could be, but there is no filler.

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

Completeness3/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 the description never says what the comparison produces (e.g., after-tax net result per strategy) or what assumptions drive it beyond 'tax treatment only'. For a 7-parameter comparison calculator, that leaves a meaningful gap in what the agent can predict before calling.

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 coverage is only 29% across 7 parameters, so the description must carry weight. It does clarify proceeds ('net sale proceeds'), a holding period, basis-via-gain, and current tax ('pay the tax'), but growth_pct, rate_later_pct, and the rural flag remain undefined in both schema and description.

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 (compares) and enumerates the three exact scenarios being compared, including the key asymmetry that 1031/DST rolls all proceeds while the OZ 2.0 fund takes only the gain. It also scopes itself with 'Tax treatment only', which separates it from single-scenario siblings like calc_oz2_benefit.

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

Usage Guidelines3/5

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

The comparative framing implies when to use it (evaluating strategies side by side), but there is no explicit when-to-use/when-not statement and no sibling is named as the alternative for a single-scenario calculation. The agent has to infer the routing logic from the enumerated strategies.

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