Skip to main content
Glama

Cash For My Note Calculators

Debt-to-income (DTI) ratio calculator

debt_to_income
Read-onlyIdempotent

The debt-to-income ratio is total monthly debt payments divided by gross monthly income, shown as a percent, and this tool computes it for a borrower (plus the housing-only ratio, if given). 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": {
      "monthly_debts": "<monthly_debts>",
      "gross_monthly_income": "<gross_monthly_income>"
    },
    "name": "debt_to_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthly_debtsYesAll monthly debt payments incl. housing, USD.
housing_paymentNoMonthly housing payment, USD (optional).
gross_monthly_incomeYesGross monthly income, USD.

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in disclosing output content: a percent plus an optional housing-only ratio, and that results are estimates rather than offers or appraisals. The vendor disclaimer about not buying notes is marginally relevant context, though it is closer to boilerplate than behavioral disclosure.

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 definition is front-loaded with the formula and result semantics in a single dense sentence, then closes with a short disclaimer. Every sentence carries some information, though the legal disclaimer is less valuable to an agent selecting the tool than the ratio definition.

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 no output schema, the description carries the burden of explaining returns, and it does indicate a percent plus an optional housing-only ratio. Precise output field names and whether both ratios are always returned are unstated, which is a minor gap for a simple deterministic calculator with a fully documented input schema.

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 (monthly_debts, housing_payment, gross_monthly_income) are already documented with units and constraints. The description's phrase 'housing-only ratio, if given' clarifies why housing_payment matters, but that meaning is largely already present in the schema, so this lands at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-and-resource ('computes' the debt-to-income ratio) and even states the formula: total monthly debt payments divided by gross monthly income, expressed as a percent. It also discloses the secondary output (housing-only ratio when housing payment is supplied), which no sibling calculator (loan_to_value, note_yield, etc.) provides.

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 explicit when-to-use or when-not-to-use guidance, and no named alternatives among the many sibling calculators. The agent must infer that this is the right tool whenever a DTI ratio is requested, with nothing indicating prerequisites or input sourcing.

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.