canadian-mortgage-deadlines
Server Details
Last day to make an offer and still fund inside a Canadian rate hold. Needs the expiry date.
- Status
- Healthy
- Uptime
- 99.9% over 42 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools.
With a single tool, naming consistency is inherently maintained.
One tool is on the low side, but for a very specific calculation (rate hold deadlines), it is reasonably scoped.
The server covers only rate hold deadlines, leaving out other common mortgage deadlines (e.g., closing deadlines), which are implied by the server name.
Available Tools
1 toolrate_hold_deadlineAInspect
Canada: the last date an offer can be accepted so a mortgage still funds before a rate hold expires. A rate hold applies to the funding date, not the offer date, so the real deadline is weeks before the printed expiry. Requires the expiry date — it cannot be answered without one.
| Name | Required | Description | Default |
|---|---|---|---|
| amount | Yes | Mortgage amount in CAD | |
| expiry | Yes | Rate hold expiry date, YYYY-MM-DD | |
| heldRate | Yes | The rate being held, as a percent, e.g. 4.79 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses key behavioral insight: the real deadline is before the printed expiry due to rate hold applying to the funding date. This adds value beyond schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences deliver purpose, context, and a usage requirement with no wasted words. Information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description implies a date output but does not specify format. For a single-value calculation tool, this is acceptable but could be slightly more explicit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers all 3 parameters with descriptions (100% coverage). The description adds minimal additional meaning, only reiterating that expiry is required. Baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly defines the tool as computing the last acceptance date for a mortgage rate hold in Canada. It uses specific context ('Canada', 'last date an offer can be accepted') and distinguishes the tool's purpose from a simple expiry lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states the prerequisite ('Requires the expiry date'), guiding when to use the tool. However, no explicit when-not or alternatives are provided, though no siblings exist to compare.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
rate_hold_deadline
Related MCP Connectors
Verified Canadian real-estate pros + housing data: prices, rates, land-transfer tax, rent-vs-buy.
Critical dates and deadlines in leases, loans, policies, HOA docs and contracts, with the clause.
Live US mortgage, auto, HELOC, personal & deposit rates with evidence, plus who can join each lender
Cited, receipt-backed US home-buying data & calculators — education-only, every number sourced.
Related MCP Servers
FlicenseNot gradedqualityBmaintenanceCanadian real estate MCP server providing verified expert lookup, market stats, current rates, land transfer taxes, and more via Cloudflare Workers.-- FlicenseNot gradedqualityBmaintenanceProvides source-dated Washington property evidence and transaction math, including REET, seller scenarios, and research packets, for software and AI assistants.-
- FlicenseNot gradedqualityCmaintenanceProvides educational fixed-rate loan estimates with mortgage and auto loan calculators.-
- AlicenseAqualityBmaintenanceDeterministic day-count and accrued-interest engine. Six ISDA/ICMA conventions, proven exact against QuantLib over 3,600 date pairs. Stops the AI guessing your interest math.355 npm1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.