Skip to main content
Glama

Cash For My Note Calculators

Partial note sale calculator

partial_purchase
Read-onlyIdempotent

In a partial note sale the holder sells only the next N payments and the rest revert to the holder, and this tool prices those payments at a target yield. It also shows what the holder keeps and the balance when payments revert. 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>",
      "payments_bought": "<payments_bought>",
      "yield": "<yield>"
    },
    "name": "partial_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNoNote interest rate, annual %. With balance, lets the tool compute the payment at full precision instead of taking payment.
yieldYesTarget yield the buyer needs, annual % (monthly compounding).
monthsYesNumber of monthly payments LEFT (not the original term).
balanceNoUnpaid principal balance in USD.
balloonNoBalloon (lump sum) due with the last payment, USD. Default 0.
paymentNoMonthly payment in USD (principal and interest).
payments_boughtYesHow many upcoming payments the buyer purchases.

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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: it discloses that outputs include the retained portion and the balance at reversion, and that results are estimates rather than offers or appraisals. This is real added value, though it doesn't discuss input combinations or edge cases (e.g. balloon handling, rate vs payment precedence).

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 scenario is front-loaded in the first sentence and the disclosure follows. The closing two sentences are partially redundant — 'Estimates, not offers or appraisals' and 'does not buy notes or make offers' restate the same disclaimer, costing a sentence that could be merged.

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?

With seven parameters, no output schema, and no nested objects, the description does the needed work: it explains the transaction, names what comes back (price, retained portion, reversion balance), and sets expectations about estimate quality. A little more on how rate and payment interact, or on balloon treatment, would make it complete.

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 seven parameters is already documented, and the baseline of 3 applies. The description adds only light conceptual framing — 'next N payments' maps to payments_bought and 'rest revert' to the retained side — but contributes nothing about rate-vs-payment interaction, balloon defaults, or units.

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 uses a specific verb-plus-resource framing: it prices the next N payments of a partial note sale at a target yield. The first sentence defines the transaction structure (holder sells N payments, rest revert), which makes the tool distinguishable from full-note tools. It never names a sibling (e.g. note_price, payment_stream_value), so differentiation is conceptual rather than explicit.

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 implied by the scenario definition — an agent can infer this is for partial sales rather than whole-note pricing. There is no explicit when-to-use/when-not guidance and no named alternative for the full-sale or payment-stream cases, leaving the agent to infer routing.

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