Skip to main content
Glama

KeyReady — Australian home loan readiness

List lender rates

list_lender_rates
Read-onlyIdempotent

Live variable principal-and-interest home loan rates, each with its comparison rate, at a given LVR from lenders’ Open Banking product data (as of 2026-11-15). Lender names are masked. Always show the comparison rate beside each rate, with the warning returned.

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": "list_lender_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
lvrNoLoan-to-value ratio, %
limitNo
purposeNoowner

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds genuinely new traits: data freshness (as of 2026-11-15), the masking of lender names, and a mandatory comparison-rate/warning pairing on output. It does not explain whether results are truncated at the limit or how ties are ordered, which is the main remaining behavioral gap.

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?

Two sentences, both front-loaded with the essential scope and the downstream obligation. Every clause carries information; nothing is redundant with the title or schema.

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?

With no output schema, the description does the job of describing returns (a rate plus its comparison rate per lender, plus a warning) and flags the name masking, so an agent knows what to expect and how to present it. Only the two undocumented parameters and the limit/truncation semantics remain unaddressed.

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

Parameters2/5

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

Schema description coverage is only 33%: 'lvr' is documented, but 'limit' and 'purpose' have no description in either the schema or the tool description. The description restates LVR but adds no meaning about valid ranges or units, and says nothing about the enum values owner/investment or what the result limit controls.

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 ('list') and a tightly scoped resource: live variable principal-and-interest home loan rates with comparison rates at a given LVR, sourced from lenders' Open Banking product data. The qualifiers (variable, P&I, live, as-of date, masked names) make it unmistakable against siblings like calculate_stamp_duty or assess_home_loan_readiness.

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

Usage Guidelines3/5

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

The description implies usage through 'at a given LVR' and gives a presentation directive ('Always show the comparison rate beside each rate, with the warning returned'), but that is output guidance rather than when-to-use guidance. It never states when to prefer this over a sibling or what scope of question it answers, leaving the agent to infer.

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.