Skip to main content
Glama
Sign In

ProprioSign

by com.propriosign
OverviewDiscussionsAdmin

Québec lease notice deadlines

notice_deadlines
Read-onlyIdempotent

Calculates when a tenant in Québec must receive the notice of rent increase or lease modification (art. 1942 C.C.Q.), whether that window is open today, and, if a receipt date is given, the date by which the tenant must reply (art. 1945 C.C.Q.). Works for fixed-term leases of 12 months or more, shorter leases, indeterminate leases and rooms.

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": {
      "lease_type": "<lease_type>"
    },
    "name": "notice_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: fr (French) or en (English). Default: fr.
roomNoTrue if the tenant rents a room (much shorter deadlines: 10 to 20 days).
lease_endNoFixed lease: last day of the lease, YYYY-MM-DD (for example 2027-06-30).
lease_typeYesfixed: the lease has an end date. indeterminate: the lease has no end date.
change_dateNoIndeterminate lease: date the change (new rent) should take effect, YYYY-MM-DD.
lease_startNoFixed lease: first day of the current lease, YYYY-MM-DD. Used to tell a lease of 12 months or more from a shorter one. If missing, 12 months or more is assumed.
receipt_dateNoOptional: date the tenant received, or will receive, the notice, YYYY-MM-DD. Gives the reply deadline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description correctly focuses on what is computed rather than safety. It adds value by naming the legal basis and the conditional second output (art. 1945 reply date) driven by receipt_date. It does not note the default language or what happens when required inputs for a given lease type are missing.

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?

Two sentences, outcome-first, with the primary computation before the conditional sub-result and the scope clause last. Slightly dense with statutory citations, but each clause carries information an agent needs.

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 seven parameters and no output schema, the description must convey the returns, and it does: deadline window, whether it is open today, and the reply deadline. Gaps are minor, such as behavior for incomplete lease-type-specific inputs.

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 coverage is 100%, so each parameter's meaning is already documented in the schema, including room, lease_start and change_date. The description only adds the link between receipt_date and the reply-deadline output and confirms the lease-type breadth, which is marginal beyond the schema.

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 (calculates) and a precise resource (Québec notice-of-rent-increase/lease-modification deadlines under art. 1942 C.C.Q.), and explicitly enumerates the three outputs. The siblings (about_propriosign, read_guide, search_guides) are all informational tools, so this computational purpose is unmistakable.

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 defines the supported lease universe (fixed 12+ months, shorter fixed, indeterminate, rooms) and says the reply deadline is produced only when a receipt date is supplied. It gives no explicit when-not-to-use or jurisdictional exclusion, though none is really needed given the unrelated siblings.

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

All ProprioSign toolsInspect
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