Skip to main content
Glama

Neofort IMO — ansambluri rezidențiale București

Calculate mortgage payment

calculate_mortgage
Read-onlyIdempotent

Indicative monthly mortgage payment, using the same formula as the calculator on neofort.ro. VAT (21%) is added to the price first, because website prices exclude VAT and the bank finances the full price. Give either a price in EUR excluding VAT or a project (its starting price is used). Defaults: 15% down payment, 25 years, 7.5% APR (DAE). Not a bank offer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_mortgage"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoLoan term in years (default 25).
dae_pctNoAnnual percentage rate (DAE) in % (default 7.5).
projectNoAlternative to price: project slug, number or name (uses its starting price).
down_payment_pctNoDown payment in % of the price incl. VAT (default 15).
price_eur_excl_vatNoApartment price in EUR, excluding VAT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds genuinely useful non-annotation context — VAT is applied before financing because website prices exclude VAT, and the explicit 'Not a bank offer' disclaimer. It does not describe the shape of the computed result beyond 'indicative monthly payment'.

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?

Three dense sentences, front-loaded with the output and the VAT rule before any parameter talk, with no filler. Slight density from nested parentheticals (21%), (DAE), but each clause carries real 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?

No output schema exists, and the description names the return value (indicative monthly payment) plus the key correctness caveat about VAT. A note on whether the result includes a breakdown or extra fees would round it out, but nothing blocks correct invocation.

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 the baseline is 3, but the description earns more by explaining the price/VAT relationship that motivates price_eur_excl_vat and by stating the down-payment, term and APR defaults in prose. It also clarifies the price-vs-project alternative that the flat schema cannot express.

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?

States a specific verb+resource (calculates an indicative monthly mortgage payment) plus the exact formula provenance (same as the calculator on neofort.ro) and the VAT precondition, which makes it unmistakable from sibling lookups like get_project or search_apartments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says how to invoke it: 'Give either a price in EUR excluding VAT or a project (its starting price is used)', and supplies fallback defaults when neither term/rate is set. It stops short of naming which sibling to use for fetching a project slug instead, so it's clear but not fully exclusionary.

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