Skip to main content
Glama

Rychlá Hypo – Czech mortgages

by cz.rychlahypo
OverviewDiscussionsAdmin

Srovnání splátek hypotéky u 6 bank

compare_mortgages
Read-onlyIdempotent

Compare the monthly payment, interest rate, RPSN (APRC), total cost and interest of a given mortgage amount across 6 Czech banks, sorted from cheapest. Applies each bank's LTV and small-loan surcharges and product limits (not creditworthiness). Above 80 % LTV banks lend only if all applicants are under 36 (set all_applicants_under_36). Use for 'which bank is cheapest for X CZK'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fixationNoRate fixation period: 1R, 3R, 5R, 7R or 10R (years). Numbers 1/3/5/7/10 are accepted too. A bank that does not offer the fixation is listed as unavailable (compare) or rejected with fixation_offered=false (max-loan).3R
term_yearsNoRepayment term in years.
loan_amountYesMortgage amount in CZK.
property_valueNoProperty price or valuation in CZK. Used for LTV surcharges and bank LTV limits. Optional.
all_applicants_under_36NoTrue if every applicant is younger than 36. Banks lend above 80 % LTV (up to 90 %) only to applicants under 36 (Czech National Bank limit); UniCredit also waives its 81–90 % LTV surcharge for them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / all_applicants_under_36 / description
      Previous value: -"True if every applicant is younger than 36 (UniCredit waives the 81–90 % LTV surcharge)."New value: +"True if every applicant is younger than 36. Banks lend above 80 % LTV (up to 90 %) only to applicants under 36 (Czech National Bank limit); UniCredit also waives its 81–90 % LTV surcharge for them."
    • changedInput schema / properties / fixation / description
      Previous value: -"Rate fixation period: 1R, 3R, 5R, 7R or 10R (years). Numbers 1/3/5/7/10 are accepted too."New value: +"Rate fixation period: 1R, 3R, 5R, 7R or 10R (years). Numbers 1/3/5/7/10 are accepted too. A bank that does not offer the fixation is listed as unavailable (compare) or rejected with fixation_offered=false (max-loan)."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, closed-world), and the description adds real behavior beyond them: it applies bank LTV and small-loan surcharges and product limits, explicitly excludes creditworthiness, and notes that a bank not offering a fixation is reported as unavailable.

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?

Three sentences, each load-bearing: what is compared and how it is sorted, what adjustments are applied, then the decision rule and a usage trigger. Nothing is repeated from the schema or annotations verbatim.

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?

With no output schema, the description still names the returned fields (monthly payment, rate, RPSN, total cost, interest) and the sort order, and it discloses the eligibility rule that can make a bank unavailable. An agent has everything needed to call and interpret this correctly.

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 baseline is 3, but the description adds cross-parameter meaning the schema does not: the >80% LTV lending rule and the flag to set (all_applicants_under_36), including UniCredit's surcharge waiver. That linkage is genuinely operational information.

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 (compare) and the exact resource (monthly payment, rate, RPSN, total cost, interest across 6 Czech banks), plus the output ordering. This clearly distinguishes it from calculate_max_mortgage and get_mortgage_rates.

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?

Gives an explicit usage trigger ("Use for 'which bank is cheapest for X CZK'") and an exclusion ("not creditworthiness"), and explains the LTV>80% under-36 condition that governs whether a quote is returned. It stops short of naming a sibling as the alternative for max-loan or rate-only queries.

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

All Rychlá Hypo – Czech mortgages toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources