Skip to main content
Glama

Cash For My Note Calculators

Payment stream present value calculator

payment_stream_value
Read-onlyIdempotent

A payment stream's lump-sum value is the present value of each future payment at a discount rate you choose, and this tool computes it for level or yearly-increasing monthly, quarterly, semiannual or annual payments, such as structured settlement, annuity or seller-carried note payments, with an optional final lump sum. Estimates, not offers or appraisals. CashForMyNote.com does not buy notes or make offers.

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": {
      "payment": "<payment>",
      "payments": "<payments>",
      "discount_rate": "<discount_rate>"
    },
    "name": "payment_stream_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentYesAmount of each payment, USD (the first year's amount if it increases).
lump_sumNoOptional lump sum, USD.
paymentsYesNumber of payments.
frequencyNomonthly (default), quarterly, semiannual or annual.
discount_rateYesDiscount rate you choose, annual % (monthly compounding).
lump_sum_monthNoMonths from today until the lump sum (required with lump_sum).
annual_increase_pctNoYearly payment increase, %. Default 0.
first_payment_monthNoMonths from today until the first payment. Default: one payment period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the result is an estimate, not an offer or appraisal, and the discount rate is user-chosen. It does not state the return shape (a single lump-sum figure) or rounding/compounding assumptions, which the schema only partly covers.

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 core computation is front-loaded in the first clause, and the supporting examples and disclaimer follow logically. It is a single long, somewhat run-on sentence, but nearly every element (payment patterns, frequencies, lump sum, estimate disclaimer) carries information an agent would otherwise lack.

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 an 8-parameter, read-only calculator with full schema coverage and no output schema, the description covers what is computed and the caveats around it. The notable gap is that with no output schema, the description does not indicate what the caller receives back (a single present-value amount), leaving the return contract implicit.

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 description coverage is 100%, so every one of the 8 parameters is already documented, making 3 the baseline. The description adds modest meaning by clarifying that payments may be level or yearly-increasing and that the final lump sum is optional, but it adds no syntax or format detail beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('computes' the 'present value' of a 'payment stream') and scopes it to level or yearly-increasing payments at monthly/quarterly/semiannual/annual frequencies with an optional lump sum. That is far more specific than a restatement of the title. It stops short of explicitly distinguishing itself from near-neighbors such as note_price or note_discount, so it does not reach a 5.

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?

Use cases are given by example (structured settlement, annuity, seller-carried note), which implies the domain where this applies. However, there is no explicit statement of when to choose this tool over a sibling like note_price or note_discount, and no prerequisites or exclusions beyond the disclaimer that it is not an offer or appraisal.

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