Skip to main content
Glama

Cash For My Note Calculators

Investment-to-value (ITV) calculator

investment_to_value
Read-onlyIdempotent

Investment-to-value (ITV) is the price paid for a note, plus any senior liens, divided by the property's value, and this tool computes ITV beside the note's loan-to-value (LTV) and the value cushion behind the investment. It shows the collateral side of a mortgage note value calculation. 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>",
      "property_value": "<property_value>"
    },
    "name": "investment_to_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesPrice paid (or being considered) for the note, USD.
balanceNoNote's unpaid balance, USD (optional, adds LTV).
senior_liensNoBalances of liens ahead of this note, USD. Default 0.
property_valueYesProperty value, USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds material context: estimates only, not offers or appraisals, and no note purchase. It also describes the calculation output (ITV, LTV, cushion), though it does not discuss rounding or precision.

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 front-loaded with the ITV definition and formula, and every sentence carries relevant scope or disclaimer information. The first sentence is long and dense, but not wasteful.

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 four-parameter, read-only calculator with no output schema and full schema coverage, the definition supplies the formula, output concepts, and key disclaimer. Minor gaps around rounding, assumptions, and explicit return field names keep it from being complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the actual formula showing price plus senior liens over property value, which clarifies how the numerator combines required and optional cost fields. It also links balance to LTV output, adding meaning beyond the field-level schema text.

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 the specific metric, gives its formula, and states it computes ITV alongside LTV and value cushion, which is a clear verb and resource. It does not explicitly contrast with the sibling loan_to_value tool, so sibling differentiation is only implicit.

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?

The phrase 'shows the collateral side of a mortgage note value calculation' implies the analysis context, but the description never states when to choose this tool over loan_to_value or other valuation siblings. No exclusions or prerequisites are given.

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.