Skip to main content
Glama

Cash For My Note Calculators

Note yield calculator

note_yield
Read-onlyIdempotent

A note's yield is the annual return that makes its remaining payments (and any balloon) worth exactly the price paid, and this tool solves for it. It assumes every payment is made on time. 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": {
      "price": "<price>",
      "payment": "<payment>",
      "months": "<months>"
    },
    "name": "note_yield"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesPrice paid for the note, USD.
monthsYesNumber of monthly payments LEFT (not the original term).
balloonNoBalloon (lump sum) due with the last payment, USD. Default 0.
paymentYesMonthly payment in USD (principal and interest).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered. The description still adds real value beyond that: the on-time-payment modeling assumption and the explicit 'estimates, not offers or appraisals' framing, which tells an agent how to present results and that no transaction is implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the definition of the quantity being solved for, followed by the assumptions and disclaimer. Nothing is redundant with the schema or the title.

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?

No output schema exists, so the description carries the burden of saying what comes back, and it never states the return form (e.g., annual yield as a percentage) or how compounding is handled. The modeling assumption and estimate disclaimer are useful, but an agent must still guess at the response shape.

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 price, payment, months, and balloon are already documented, including that months is payments left rather than original term. The description reinforces the conceptual relationship between price, payments, and balloon but adds no syntax, units, or edge-case detail beyond the schema; baseline 3 applies.

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?

States a specific verb ('solves for') and a well-defined quantity: the annual return equating remaining payments plus any balloon to the price paid. An agent can tell this computes yield, but the description never distinguishes it from siblings like early_payoff_yield, yield_ladder, or effective_annual_rate, so the boundary is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not guidance, and no alternative named. The closest thing to context is the modeling assumption ('assumes every payment is made on time') and the 'estimates, not offers or appraisals' caveat, which constrain interpretation but do not tell an agent when to pick this tool over its siblings.

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