mortgage-tools

create_enquiry

Submit a mortgage enquiry to Manage Your Loans on the customer's behalf so a broker contacts them. ONLY call this after the person has explicitly agreed to be contacted — pass consent=true. Do not invent details; ask the user.

Args:
    firstName: Customer's first name.
    lastName: Customer's last name.
    email: Customer's email address.
    phone: Australian phone number (04.., 02/03/07/08.., or 1300/1800).
    consent: MUST be true — the customer's explicit agreement to be contacted.
    loanType: e.g. "Home Loan", "Refinance", "Investment Property" (optional).
    loanAmount: Approximate loan amount, free text (optional).
    message: Anything else the customer wants the broker to know (optional).
    isCostco: True if this is a Costco-member enquiry.
    costcoMembershipNumber: Costco membership number if provided (optional).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	Yes
`phone`	Yes
`consent`	Yes
`message`	No
`isCostco`	No
`lastName`	Yes
`loanType`	No
`firstName`	Yes
`loanAmount`	No
`costcoMembershipNumber`	No

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description partially covers behavioral traits: it implies a write operation and emphasizes consent. However, it does not disclose error handling, idempotency, or the consequences of missing consent, leaving gaps for an AI agent.

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?

The description is well-organized with a clear lead sentence followed by a parameter list. It is not overly verbose, but some parameter descriptions (e.g., firstName) are slightly redundant with the field name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 10 parameters and no output schema, the description covers arguments well but omits return value or success/failure indicators. It also does not mention prerequisites like authentication, leaving the completion incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds substantial meaning beyond the empty schema: it explains phone format requirements, consent requirement, optionality, and the purpose of isCostco. The schema coverage is 0%, so the description fully compensates.

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 submits a mortgage enquiry on behalf of the customer, and the sibling tools (calculate_repayments, check_costco_eligibility, etc.) are distinct, making the purpose unambiguous.

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 explicitly states when to call this tool ('after the person has explicitly agreed to be contacted') and provides a critical condition ('pass consent=true'). It also warns against inventing details, giving clear usage boundaries.

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

All mortgage-tools 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.2/5.0

Disambiguation5/5

Each tool targets a distinct aspect of the mortgage process: repayment calculation, Costco eligibility, loan type comparison, enquiry submission, borrowing power estimation, and rate guidance. There is no functional overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., calculate_repayments, check_costco_eligibility, compare_loan_types), using lowercase with underscores.

Tool Count5/5

With 6 tools, the set is well-scoped for a mortgage advisory server, covering key pre-application steps without being overly large or too sparse.

Completeness4/5

The tools cover the core pre-application workflow: calculation, borrowing power, rate guidance, comparison, eligibility, and enquiry. A minor gap is the lack of tools for existing loan management or detailed offer comparison.

Resources

Need Help?