EZ Annuity

Value a payment stream or judge an offer

value_payment_stream

Read-only

Present value of a structured settlement, annuity or lottery payment stream at typical buyer discount rates (8% to 18%), and, if a lump-sum offer is given, the effective discount rate that offer implies, the cents on the dollar, and whether it sits in the typical range. With targetAmount, also prices a partial sale (sell only enough payments to raise that amount and keep the rest). Use when someone asks what their payments are worth, whether an offer is fair, or what selling part of their payments would cost.

Input Schema

Name	Required	Description
`count`	No	Number of payments left (give this, or years and/or months)
`offer`	No	Lump sum a buyer has offered for these payments, in US dollars (optional)
`years`	No	Years of payments left (alternative to count)
`months`	No	Extra months of payments left (used with years)
`payment`	Yes	Amount of each payment in US dollars
`frequency`	Yes	How often the payments arrive
`targetAmount`	No	Lump sum wanted from a PARTIAL sale, in US dollars (optional). Returns partial_sale: what it costs to raise this amount by selling the next payments in full, or a slice of every payment, at 8%, 13% and 18%.
`lifeContingent`	No	true if the payments stop at the recipient's death
`startsInMonths`	No	Months until the first payment, if the payments have not started yet (default 0)
`annualIncreasePct`	No	Yearly step-up in the payment, in percent (for example 3 for 3% a year)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / targetAmount

Added value: +{
+  "description": "Lump sum wanted from a PARTIAL sale, in US dollars (optional). Returns partial_sale: what it costs to raise this amount by selling the next payments in full, or a slice of every payment, at 8%, 13% and 18%.",
+  "type": "number"
+}

First observedOct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only say readOnlyHint=true and openWorldHint=false, so the description carries the burden and does well: it discloses the 8%-18% discount-rate band, the typical range check, cents-on-the-dollar output, and the partial-sale behavior. It does not discuss sensitivity/assumptions (e.g. life-contingent mortality handling), but it adds substantial context beyond the annotations.

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 the core computation, then progressive elaboration on offer and targetAmount, ending with usage triggers. Dense but every clause adds function; the nested parentheticals make it slightly heavy but not wasteful.

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?

For a 10-parameter computation tool with no output schema, the description adequately explains both primary and conditional outputs (offer metrics, partial_sale). Minor gaps remain around assumption sensitivity and the lifeContingent/step-up interactions, but an agent has enough to invoke it correctly.

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 description coverage is 100%, so baseline is 3. The description nonetheless adds real meaning beyond the schema: it explains what 'offer' produces (effective rate, cents on the dollar, range check) and what targetAmount does (partial sale returning full-payment vs sliced-payment options at 8/13/18%), which the schema only partially conveys.

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 precise verb+resource: present value of a structured settlement/annuity/lottery payment stream, plus offer judging and partial-sale pricing. An agent can identify exactly what computation this performs and how it differs from the sibling tools (index lookup, state lists, transfer rules).

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?

Explicitly names the triggering situations: 'what their payments are worth, whether an offer is fair, or what selling part of their payments would cost.' Clear context, though it offers no exclusions or alternatives, which is acceptable given the siblings are unrelated reference tools.

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

All EZ Annuity tools Inspect

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

Need Help?