Skip to main content
Glama

SA Property Costs

Calculate home loan repayment

bond_repayment
Read-only

Calculates the monthly repayment, total interest and total repaid for a South African home loan (bond). Requires the interest rate because rates change — use prime ± the bank's margin.

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": {
      "loan_amount": "<loan_amount>",
      "annual_interest_rate_pct": "<annual_interest_rate_pct>"
    },
    "name": "bond_repayment"
  }
}

Input Schema

NameRequiredDescriptionDefault
term_yearsNoLoan term in years. Default 20
loan_amountYesAmount borrowed, in rand
annual_interest_rate_pctYese.g. 10.75

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / loan_amount / description
      Added value: +"Amount borrowed, in rand"
    • addedInput schema / properties / term_years / description
      Added value: +"Loan term in years. Default 20"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully discloses the three returned figures (important since there is no output schema), but omits modelling assumptions such as constant rate, monthly compounding, and whether fees or insurance are included in the repayment.

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?

Two short sentences, front-loaded with what the tool produces and followed by the one non-obvious input constraint. The 'because rates change' rationale is mild filler but still justifies the requirement.

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?

For a simple three-parameter read-only calculator with no output schema, the description covers purpose, the key rate input, and the return values. Remaining gaps are the amortization assumptions and whether extra bond costs are included, which would matter to an agent verifying results.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning to annual_interest_rate_pct by explaining it should be derived as prime plus a bank margin and that rates change. It adds nothing for term_years or loan_amount beyond the schema.

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?

States a specific verb (calculates) and resource (monthly repayment, total interest, total repaid for a South African home loan), which is clearly distinct from the rate/duty/cost siblings. It does not explicitly name or contrast with any sibling tool, so it stops short of a 5.

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 gives guidance on obtaining the rate (prime ± bank margin), which is parameter-level help rather than when-to-use guidance. It never states when to pick this tool over purchase_costs or municipal_rates, or what prerequisites apply; the usage context is only implied by the domain.

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