Skip to main content
Glama
Sign In

MyLastWill

by org.mylastwill
OverviewDiscussionsAdmin

Estimate federal estate tax and check state estate taxes

estimate_estate_tax
Read-onlyIdempotent

Estimate U.S. federal estate tax for deaths in 2027 and whether the person's state estate or inheritance tax may apply, including how much a charitable gift in the will saves. Federal tax is 40% of the taxable estate above the exemption ($15.48 million per person in 2027). For married couples it assumes everything passes to the spouse first and estimates tax at the second death with both exemptions. State results flag thresholds and top rates rather than computing state tax. General information, not tax advice.

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": {
      "estate_value": "<estate_value>"
    },
    "name": "estimate_estate_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoU.S. state (or DC) of residence: full name or two-letter code.
marriedNoTrue if married to a U.S. citizen.
estate_valueYesTotal value in USD of everything the person owns, including home, investments, retirement accounts and life insurance they own, minus debts.
charitable_giftNoDollar amount left to charity at death (optional).
lifetime_taxable_giftsNoTotal taxable gifts made during life above the annual exclusion (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real behavioral detail: the 40% rate and $15.48M 2027 exemption, the spousal-first pass-through assumption for married couples, and the shallow depth of state results. It stops short of describing result shape or rounding/output format, but the modeling assumptions are well disclosed.

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?

Front-loaded with purpose, then mechanisms, then caveats; four dense sentences with no filler. The middle sentences pack several clauses each, which slightly hurts scannability but every clause carries information.

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?

With no output schema, the description must convey return content, which it only partially does — it says state results 'flag thresholds and top rates' but not what the federal result looks like (single number, breakdown, assumptions echoed). It is adequate for a calculator but leaves the output shape underspecified.

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%, so baseline is 3; the description adds genuine modeling semantics beyond the schema — that `married` triggers an unlimited-marital-deduction assumption and taxation at second death with both exemptions, and that `charitable_gift` produces a quantified savings figure. These meanings are not derivable from the field descriptions alone.

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 (estimate) and resource (U.S. federal estate tax) with an explicit scope of 2027 deaths, plus two secondary capabilities: state threshold flagging and charitable-gift savings. This clearly separates it from the sibling will-authoring tools (create_will, add_charity_to_existing_will) without needing to name them.

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?

Implies usage through scope statements (2027 deaths, U.S. states/DC) and includes a 'general information, not tax advice' disclaimer, but never states when to prefer this over an alternative or what inputs make it inapplicable. Usage is inferable rather than prescribed.

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

All MyLastWill toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources