Skip to main content
Glama

Cash For My Note Calculators

Note value at several yields

yield_ladder
Read-onlyIdempotent

A note's price falls as the yield a buyer requires rises, and this tool prices the same remaining payments at up to 12 yields side by side to show how much. 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": {
      "months": "<months>",
      "yields": "<yields>"
    },
    "name": "yield_ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNoNote interest rate, annual %. With balance, lets the tool compute the payment at full precision instead of taking payment.
monthsYesNumber of monthly payments LEFT (not the original term).
yieldsYesYields to test, annual %.
balanceNoUnpaid principal balance in USD, greater than 0.
balloonNoBalloon (lump sum) due with the last payment, USD. Default 0.
paymentNoMonthly payment in USD (principal and interest).

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by framing results as estimates, not offers or appraisals, and by noting the site does not buy notes. It does not describe the shape of the result (a yield-to-price table) or how many rows come back.

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 economic rationale is front-loaded, then the mechanic, then the disclaimer, with no filler sentences. The disclaimer occupies roughly a third of the text but is arguably necessary for a financial-estimate tool.

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 carries the burden of explaining what comes back, and 'prices ... side by side to show how much' only loosely implies a yield/price table without stating the returned fields or ordering. For a 6-parameter valuation tool this is adequate but leaves a meaningful gap on return values.

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 the schema already documents every parameter, including the rate+balance vs payment alternative and that months means remaining payments. The description only restates the 12-yield cap already enforced by maxItems, adding no new parameter meaning.

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 states a concrete verb and resource: it prices a note's remaining payments at multiple yields side by side (up to 12). The phrase 'the same remaining payments at up to 12 yields' distinguishes it from a single-yield pricing tool, though it never names a sibling to contrast with explicitly.

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?

Usage is only implied through the economic framing ('price falls as yield rises'), which suggests a sensitivity/comparison scenario, but there is no explicit 'use this when you need a yield sensitivity table rather than a single yield' and no exclusions or prerequisites.

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