Skip to main content
Glama
tresor4k

macalc

calculate_us_mortgage

Estimate US mortgage payments with PMI, property tax, and insurance. Input home price, down payment percentage, annual rate, and loan term to get monthly principal, interest, PMI, tax, and insurance estimates.

Instructions

Calculate US mortgage with PMI, property tax, and insurance estimates. Returns: {home_price, down_payment, loan_amount, monthly_pi, monthly_pmi, monthly_property_tax, ...}. See list_bundles for related 'finance-us' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
home_priceYesHome purchase price in USD
down_payment_pctNoDown payment percentage (default 20%)
annual_rateYesAnnual mortgage interest rate in %
yearsNoLoan term in years (default 30)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, authentication needs, or the nature of 'estimates'. The list of return fields offers some transparency, but overall the description does not adequately explain what the tool does beyond its purpose.

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?

The description is two sentences, front-loaded with purpose, and includes return fields and a pointer to related tools. Every sentence serves a purpose without extraneous information.

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?

The description covers the main purpose and return fields. However, it lacks explanation of calculation assumptions (e.g., how PMI is estimated) and the presence of an output schema is not leveraged. Still, it is adequate for a calculation tool.

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 coverage is 100%, so baseline is 3. The description does not add additional meaning beyond the schema's parameter descriptions. It mentions return fields but not parameter details.

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 clearly states 'Calculate US mortgage with PMI, property tax, and insurance estimates' – a specific verb and resource. It distinguishes from sibling tools like 'calculate_mortgage' by being US-specific and including additional components.

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 description mentions 'See list_bundles for related 'finance-us' calculators', providing a pointer to alternatives but does not explicitly state when to use this tool versus other mortgage calculators. Usage context is implied but not fully specified.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server