Clara Mortgage Assistant

Refuse Unsupported Mortgage Approval or Underwriting Requests

refuse_unsupported_mortgage_request

Read-onlyIdempotent

MUST be called whenever the user asks whether a borrower should be approved, denied, pre-approved, conditionally approved, underwritten, or assessed for suitability. Also call it for lender or product recommendations, borrower documents or accounts, current rates or rules, submissions, outreach, or anything outside Clara Mortgage Assistant calculations. This tool returns the required deterministic refusal. Send only the matching requestType category—never include the original prompt, names, identifiers, document content, or other user data. Do not answer these requests directly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`requestType`	Yes	Category of unsupported request. Do not include or infer any user, borrower, account, or document data.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tool`	Yes
`status`	Yes
`message`	Yes
`requestType`	Yes
`dataHandling`	Yes
`safeAlternative`	Yes

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses that the tool returns a deterministic refusal, must not receive the original prompt or user data, and should not be used to answer requests directly. This adds meaningful behavioral and privacy context.

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 front-loaded with the critical MUST-call instruction, then efficiently lists trigger categories, return behavior, and data-handling rules. Every sentence adds necessary information without redundancy.

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 output schema exists, the description does not need to explain return values. It fully covers when to use the tool, what requestType to send, what not to include, and how to behave, making it complete for an agent to select and invoke 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?

The schema already provides full enum coverage and a description for requestType. The tool description adds useful guidance to send 'only the matching requestType category' and never include original prompt or user data, reinforcing safe parameter selection, though it does not map specific scenarios to enum values.

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 clearly states the tool's purpose: to refuse unsupported mortgage approval, underwriting, and related requests. It lists specific trigger categories and explicitly distinguishes the tool from Clara Mortgage Assistant calculations, which also separates it from the sibling calculation tools.

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 gives explicit when-to-use guidance with 'MUST be called whenever' and enumerates many concrete scenarios. It also clarifies that this tool is for anything 'outside Clara Mortgage Assistant calculations,' effectively directing supported calculation requests to the sibling tools.

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?