Skip to main content
Glama

Cash For My Note Calculators

Loan-to-value (LTV) ratio calculator

loan_to_value
Read-onlyIdempotent

The loan-to-value ratio is the loan balance divided by the property's value, shown as a percent, and this tool computes LTV, combined LTV (CLTV) with other liens, and the equity cushion behind a note. 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": {
      "loan": "<loan>",
      "value": "<value>"
    },
    "name": "loan_to_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
loanYesNote balance, USD.
valueYesProperty value, USD.
other_liensNoBalances of other liens on the property, USD. Default 0.

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, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds the meaningful caveat that results are estimates rather than offers or appraisals, plus a vendor disclaimer, but says nothing about return format or precision beyond that.

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: the first defines the metric and states what the tool computes, the second bounds the output. No redundant clauses, and the substantive capability statement leads before the disclaimer.

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 three-parameter, annotation-covered, read-only calculator with no output schema, the description covers inputs conceptually and identifies the three outputs (LTV, CLTV, equity cushion). Only the shape or units of the returned values are left implicit, which is a minor gap.

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 all three parameters, including other_liens, are already documented with types and defaults. The description adds only conceptual framing by mentioning combined LTV with other liens and the equity cushion, without new syntax, units, or edge-case behavior beyond the schema.

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 specific verbs and resources: it computes LTV (loan balance divided by property value as a percent), combined LTV including other liens, and the equity cushion behind a note. That distinguishes it from neighbors such as investment_to_value or debt_to_income without naming them, though no sibling is explicitly excluded.

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?

There is no when-to-use or when-not-to-use guidance and no routing to alternatives like investment_to_value for a different ratio. The only constraint offered is that outputs are estimates, not offers or appraisals, which is a limitation rather than a usage rule.

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