Clara Mortgage Assistant

Estimate a Mortgage Prepayment Penalty

estimate_prepayment_penalty

Read-onlyIdempotent

Estimate three-months-interest and simple IRD prepayment penalties; lender discharge statements remain authoritative. Use only with explicit, non-identifying numeric inputs. Calculation only: never use this tool to approve, deny, underwrite, recommend, select a lender or product, or fill missing inputs from prior chats, files, accounts, documents, websites, or web search.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`method`	No
`principal`	Yes	Outstanding mortgage balance in Canadian dollars.
`annualRate`	Yes	Current annual mortgage rate. Supply the annual rate as a decimal; for example, 5.25% is 0.0525.
`jurisdiction`	No	Canadian calculations only.	CA
`effectiveDate`	Yes	Date the supplied rates and policy assumptions were confirmed.
`comparisonRate`	No	Annual comparison or reference rate used for the simplified interest-rate-differential estimate. Supply the annual rate as a decimal; for example, 5.25% is 0.0525.
`remainingTermMonths`	Yes	Number of months remaining in the mortgage term.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tool`	Yes
`currency`	Yes
`disclaimer`	Yes
`calculation`	Yes
`jurisdiction`	Yes
`effectiveDate`	Yes
`calculationVersion`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds important behavioral context: lender discharge statements remain authoritative, calculations are estimates only, and the tool must not be used for decisions or to fill missing inputs. This meaningfully discloses limitations and expected behavior.

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 the core purpose, followed by concise usage restrictions. Every sentence earns its place with no redundancy or filler.

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?

Given the strong annotations, rich input schema, and existing output schema, the description fully covers purpose, limitations, and usage boundaries. It is complete for an agent to select and invoke the tool correctly.

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 high (86%), so the schema already documents most parameters. The description adds context about the two calculation methods but does not add significant per-parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 uses a specific verb ('Estimate') and resource ('Mortgage Prepayment Penalty'), and explicitly names the two calculation types ('three-months-interest and simple IRD'). This clearly distinguishes it from sibling tools like calculate_ltv or calculate_qualification.

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

Usage Guidelines5/5

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

The description provides explicit usage constraints: 'Use only with explicit, non-identifying numeric inputs' and 'never use this tool to approve, deny, underwrite, recommend, select a lender or product, or fill missing inputs from prior chats, files, accounts, documents, websites, or web search.' This gives clear when-to-use and when-not-to-use guidance.

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

All Clara Mortgage Assistant tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each calculation tool targets a distinct mortgage calculation (debt service ratios, LTV, qualification, scenario comparison, prepayment penalty), and the refuse tool exists solely for disallowed requests, creating clear boundaries between tools. The descriptions are explicit about when to use each tool and how they differ, minimizing misselection risk.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (calculate_debt_service, calculate_ltv, calculate_qualification, compare_mortgage_scenarios, estimate_prepayment_penalty). One tool deviates with the verb 'refuse' rather than 'calculate' or 'estimate', which is appropriate given its distinct refusal purpose but slightly inconsistent in naming style.

Tool Count4/5

With 6 tools, the count is well-scoped for a specialized mortgage calculation assistant. Each tool addresses a specific calculation or a necessary refusal flow, and the count is neither too thin nor too heavy for the stated purpose.

Completeness4/5

The set covers the main mortgage calculations an agent would need (debt service, LTV, qualification, comparisons, prepayment penalties), with a dedicated refusal tool for unsupported requests. A minor gap might be tools for other common calculations like maximum purchase price or payment amount, but the core domain appears covered.

Resources

Need Help?