Skip to main content
Glama

OZ 1.0 Dec 31, 2026 inclusion estimate

calc_2026_inclusion
Read-onlyIdempotent

Amount of deferred gain included on Dec 31, 2026 for a pre-2027 QOF investment, with the 10%/15% basis step-up where the holding period was met, and an estimated tax at the user's rate.

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": {
      "deferred_gain": "<deferred_gain>",
      "invest_date": "<invest_date>"
    },
    "name": "calc_2026_inclusion"
  }
}

Input Schema

NameRequiredDescriptionDefault
rate_pctNo
invest_dateYes
deferred_gainYes
fmv_12_31_2026No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context: the 10%/15% basis step-up applies only when the holding period was met, and tax is estimated at the user's rate. It still omits return format and calculation assumptions.

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 definition is one dense sentence with no filler, front-loading the result and date. It could be split for readability, but every clause adds scope or calculation logic.

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?

For a four-parameter calculator with no output schema and 0% schema descriptions, the description explains the core computation but leaves key inputs and the return shape underspecified. It is adequate to understand the purpose but not fully sufficient to invoke correctly without inspecting the schema.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It references deferred gain, the user's rate, and the holding period/date indirectly, but never explains fmv_12_31_2026, date format, or whether rate_pct is a percentage or decimal.

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 states a precise calculation: deferred gain inclusion on Dec 31, 2026 for a pre-2027 QOF investment, including the basis step-up and estimated tax. The 'pre-2027 QOF' scope clearly distinguishes it from OZ 2.0-related sibling calculators.

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?

It specifies the applicable scenario (pre-2027 QOF investment) but gives no explicit when-to-use/when-not guidance or named alternatives among the many calc_* siblings. Usage is implied by the scope rather than stated.

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