Skip to main content
Glama

Cash For My Note Calculators

Note discount calculator

note_discount
Read-onlyIdempotent

A note's discount is how far its price is below the unpaid balance, and this tool gives it in dollars, as a percent, and in cents per dollar of balance. 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>",
      "balance": "<balance>"
    },
    "name": "note_discount"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesPrice, USD.
balanceYesUnpaid principal balance in USD, greater than 0.

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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by specifying the output forms (dollars, percent, cents per dollar) and clearly framing results as estimates, not offers or appraisals. It does not explain edge cases such as a price above balance, but the added context is meaningful for a simple calculator.

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 description is compact and front-loads the core definition before stating output units and disclaimers. The disclaimer sentences are relevant but slightly less tightly connected to the calculation itself, keeping this from being maximally concise.

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 simple two-parameter read-only calculator with no output schema, the description gives adequate completeness by explaining the concept, output forms, and the estimate-only limitation. It could be marginally stronger by noting how a price above the unpaid balance is treated, but no critical information is missing.

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?

The input schema has 100% description coverage for both required parameters (price and balance), so the schema already carries the parameter documentation burden. The description restates the price-versus-balance relationship conceptually but does not add format, unit, or validation details beyond what the schema provides.

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 clearly defines what a note discount is and states that the tool returns it in three forms: dollars, percent, and cents per dollar of balance. It is specific about the calculation, though it does not explicitly distinguish this tool from siblings such as note_price or note_yield.

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 definition of the calculation, and the disclaimer clarifies that results are estimates rather than offers or appraisals. However, there is no explicit guidance on when to use this tool versus related sibling tools like note_price or note_yield.

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