canadian-mortgage-deadlines

rate_hold_deadline

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "expiry": "<expiry>",
      "heldRate": "<heldRate>",
      "amount": "<amount>"
    },
    "name": "rate_hold_deadline"
  }
}

Input Schema

Name	Required	Description
`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

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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.

Conciseness5/5

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.

Completeness4/5

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.

Parameters3/5

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.

Purpose5/5

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.

Usage Guidelines4/5

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.

All canadian-mortgage-deadlines tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?