Skip to main content
Glama
Sign In

CalcBright Calculators

by com.calcbright
OverviewDiscussionsAdmin

Debt-to-Income Calculator

debt_to_income_calculator
Read-onlyIdempotent

A 35% debt-to-income ratio passes most US lenders. Gulf banks cap installments at 50% of salary in the UAE, 33.33% in Saudi Arabia and 40% in Kuwait. Web page: https://calcbright.com/debt-to-income-calculator

Input Schema

NameRequiredDescriptionDefault
autoNoCar loan installments
cardsNoCredit card minimum payments
otherNoOther debt payments Overdraft and buy-now-pay-later installments, child support, alimony.
rulesNoLender rules Gulf central banks cap the share of salary that loan installments may take; US lenders use guideline ratios.us
earnerNoIncome from Retirees have a lower cap: 30% of the pension in the UAE and Kuwait, 25% in Saudi Arabia.salary
incomeNoGross monthly income Before tax and deductions – in Kuwait, salary after deductions.
housingNoMonthly rent Gulf banks leave rent out of the debt burden ratio; US lenders count it, or the new mortgage payment with tax and insurance.
studentNoStudent loan payments
currencyNoCurrencyUSD
personalNoPersonal loan installments
cardLimitNoTotal credit card limits Optional. Many UAE banks count 5% of every card limit, used or not, instead of the minimum payment.
housingTypeNoHousing payment isrent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / auto / description
      Previous value: -"Car loan payments"New value: +"Car loan installments"
    • addedInput schema / properties / cardLimit
      Added value: +{
+  "description": "Total credit card limits Optional. Many UAE banks count 5% of every card limit, used or not, instead of the minimum payment.",
+  "maximum": 1000000000,
+  "minimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / cards / description
      Previous value: -"Credit card minimums"New value: +"Credit card minimum payments"
    • addedInput schema / properties / earner
      Added value: +{
+  "default": "salary",
+  "description": "Income from Retirees have a lower cap: 30% of the pension in the UAE and Kuwait, 25% in Saudi Arabia.",
+  "enum": [
+    "salary",
+    "pension"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / housing / description
      Previous value: -"Rent or mortgage payment"New value: +"Monthly rent Gulf banks leave rent out of the debt burden ratio; US lenders count it, or the new mortgage payment with tax and insurance."
    • addedInput schema / properties / housingType
      Added value: +{
+  "default": "rent",
+  "description": "Housing payment is",
+  "enum": [
+    "rent",
+    "loan"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / income / description
      Previous value: -"Gross monthly income Before tax and deductions."New value: +"Gross monthly income Before tax and deductions – in Kuwait, salary after deductions."
    • changedInput schema / properties / other / description
      Previous value: -"Other debt payments Personal loans, child support, alimony, etc."New value: +"Other debt payments Overdraft and buy-now-pay-later installments, child support, alimony."
    • addedInput schema / properties / personal
      Added value: +{
+  "default": 0,
+  "description": "Personal loan installments",
+  "maximum": 100000000,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / rules
      Added value: +{
+  "default": "us",
+  "description": "Lender rules Gulf central banks cap the share of salary that loan installments may take; US lenders use guideline ratios.",
+  "enum": [
+    "us",
+    "ae",
+    "sa",
+    "kw",
+    "om",
+    "bh"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world). The description adds genuine domain context — that Gulf banks cap installments at 50%/33.33%/40% of salary and retirees get lower caps — which helps interpret the result. However, it never says what the tool returns (a ratio, a pass/fail per rule, both), and there is no output schema to fall back on.

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

Conciseness3/5

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

Only three sentences, but they are spent entirely on regulatory trivia and a promotional URL rather than on what the tool does. The link earns no place in a tool definition, and the core statement of purpose is missing entirely.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 parameters, four enums, and no output schema, the description should explain the output shape and how the rules/earner switches change the result. Instead it supplies peripheral facts and a website link, leaving the agent to guess what comes back.

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%, including notes on the rules enum and the retiree cap, so the schema does the heavy lifting. The description adds nothing about which parameters to set (rules, earner, housingType) beyond loosely echoing the thresholds already in the schema text. Baseline 3 applies.

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

Purpose3/5

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

The reader can infer the domain (debt-to-income) from the name and from the lender-threshold facts, but the description never states the action: it never says the tool computes a DTI ratio from income and debt inputs. Nothing distinguishes it from siblings like home_affordability_calculator or loan_calculator.

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 guidance, no mention of alternatives, no note that this is for qualifying for a loan versus tracking payoff (debt_payoff_calculator). The thresholds hint at the use case but never state it explicitly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CalcBright Calculators toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources