Skip to main content
Glama

FigureDeck US Mortgage Data

How much house a given income supports

affordability

Works backwards from income to a purchase price. Applies a debt-to-income cap to gross monthly income, subtracts existing monthly debts, then subtracts property tax, insurance and HOA, and solves for the loan that the remaining monthly budget supports at the given rate. Adds the down payment to get the price. Also returns the same answer at the 28%, 36%, 43% and 50% DTI caps so the caller can see how much the choice of cap moves the number.

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_income": "<monthly_income>",
      "annual_rate_percent": "<annual_rate_percent>",
      "term_years": "<term_years>"
    },
    "name": "affordability"
  }
}

Input Schema

NameRequiredDescriptionDefault
term_yearsYesTerm in years, e.g. 30.
monthly_hoaNoOptional monthly HOA in dollars.
monthly_taxNoOptional monthly property tax in dollars.
down_paymentNoCash available for down payment in dollars. Default 0.
monthly_debtsNoExisting monthly debt payments (car, student, cards) in dollars. Default 0.
monthly_incomeYesGross monthly income in dollars. Monthly, not annual — divide by 12 first.
dti_cap_percentNoWhich DTI cap to headline. Default 36.
monthly_insuranceNoOptional monthly homeowners insurance in dollars.
annual_rate_percentYesExpected nominal annual rate in percent, e.g. 6.5.

Output Schema

NameRequiredDescriptionDefault
bandsYes
citationYes
dti_usedYes
max_loanYes
max_priceYes
down_paymentYes
max_monthly_piYes
max_monthly_housing_budgetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the actual calculation sequence (DTI cap on gross income, minus debts, minus tax/insurance/HOA, solve for loan, add down payment) so the agent can predict the output. It also reveals a non-obvious behavior — that the response includes the same figure at 28%, 36%, 43% and 50% caps — which no schema field would convey. It does not state that the tool is a pure computation with no side effects, but that is strongly implied by the arithmetic narrative.

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 core operation is front-loaded in the first sentence and the computation chain follows logically. Four sentences is a reasonable length for a nine-parameter calculator, though the final sentence about the alternate DTI caps is slightly repetitive in phrasing.

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

Completeness5/5

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

For a nine-parameter financial calculator with an output schema already covering return values, the description supplies the algorithm, the direction of the calculation, and the multi-scenario return behavior. Nothing an agent needs in order to call it correctly is missing.

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 a baseline of 3 would be defensible, but the description goes further by explaining how the inputs interact — debts are subtracted from the capped budget, tax/insurance/HOA are carried costs, down payment is added back at the end, and dti_cap_percent selects the headline scenario. That relational meaning is not present in the per-field 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 opening sentence names a specific inverse operation — 'works backwards from income to a purchase price' — which is far more informative than the title and implicitly separates it from a forward mortgage_payment calculator. It stops short of naming a sibling explicitly, so an agent must infer the boundary rather than read it.

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 phrase 'works backwards from income,' which tells the agent this is the affordability direction rather than the payment direction. There is no explicit when-to-use/when-not-to-use statement and no reference to mortgage_payment or search_conforming_limits, so the agent gets context but no routing 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