Skip to main content
Glama

MRK Dubai Property

Mortgage repayment

calculate_mortgage
Read-onlyIdempotent

Monthly repayment, total interest and loan-to-value for a repayment mortgage. Pure arithmetic on the rate you supply; UAE Central Bank base rate is returned for context only, not as a quote.

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": {
      "priceAed": "<priceAed>",
      "annualRatePct": "<annualRatePct>"
    },
    "name": "calculate_mortgage"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoTerm in years (default 25, UAE max 25)
priceAedYesProperty price in AED
annualRatePctYesAnnual interest rate in % (e.g. 4.25)
downPaymentPctNoDown payment as % of price (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent and closed-world behaviour, and the description still adds real value: 'pure arithmetic on the rate you supply' tells the agent results are deterministic derivations from user input, not market quotes, and the base-rate disclaimer prevents misreading a context figure as an offer. It stops short of stating assumptions (fees, insurance, whether downPaymentPct reduces the loan) or that figures are illustrative estimates.

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 tight sentences: the first front-loads what is returned, the second eliminates the most likely misinterpretation. No filler or repetition of the name or schema.

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 return-value burden and does it by enumerating the three computed figures plus the contextual base rate. A brief statement of modelling assumptions (fees, insurance, or that outputs are illustrative) would close the remaining gap for a financial calculator.

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 the schema already documents priceAed, annualRatePct, years and downPaymentPct. The description only gestures at the rate parameter ('the rate you supply') and adds no semantics for term or down payment, so it meets the baseline without exceeding it.

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?

Names the concrete outputs (monthly repayment, total interest, loan-to-value) for a specifically scoped resource (repayment mortgage), which an agent can distinguish from siblings like calculate_purchase_costs or rental_yield_estimate. It never names those alternatives explicitly, so the differentiation is implicit rather than stated.

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 narrow scope (mortgage repayment math), and the note about the Central Bank base rate being 'context only, not a quote' usefully signals this is not a rate-lookup tool. However, there is no explicit when-to-use versus when-not, nor a pointer to the purchase-cost or buying-cost calculators that an agent might confuse it with.

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