Contract Lily

Northern Ireland rent increase check

check_northern_ireland_rent_increase_notice

Read-onlyIdempotent

Check a landlord's rent increase notice, given from 1 April 2025, for a private tenancy in Northern Ireland other than a controlled tenancy (do not use it for a controlled tenancy, which has different rules): whether it is in writing, whether the new rent starts at least three months after the notice is given, and whether it comes at least 12 months after the tenancy began and the last increase; and when the new rent can start. Northern Ireland only; it does not judge whether the new rent is fair.

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": {
      "history": "<history>",
      "received": "<received>",
      "starts": "<starts>",
      "tenancyStart": "<tenancyStart>",
      "written": "<written>"
    },
    "name": "check_northern_ireland_rent_increase_notice"
  }
}

Input Schema

Name	Required	Description
`starts`	Yes	The day the notice says the new rent starts, as YYYY-MM-DD.
`history`	Yes	Whether the rent has gone up before: none, increased (give lastIncrease), or unknown.
`written`	Yes	Whether the notice is in writing; an email, text or other electronic message counts.
`received`	Yes	The day the tenant was given the notice, as YYYY-MM-DD; from 1 April 2025.
`lastIncrease`	No	If the rent went up before, the day that increase took effect, as YYYY-MM-DD.
`tenancyStart`	Yes	The day the tenancy was granted, as YYYY-MM-DD.

Output Schema

Name	Required	Description	Default
`page`	Yes
`checks`	Yes
`lawAsAt`	Yes
`summary`	Yes
`earliestAllowed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.6/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 safety is covered. The description adds value beyond that by declaring the legal scope of the judgment and the explicit limitation on fairness assessment. It stops short of saying what form the result takes, which the output schema covers.

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?

A single dense sentence, but front-loaded with the object of the check and the jurisdiction, with the rule list following. The parenthetical exclusion is placed where it is most needed. Slightly long for one sentence but every clause carries legal meaning.

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

Completeness5/5

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

Covers jurisdiction, effective-date scope, tenancy type, the conditions evaluated, the exclusion, and the limit of the judgment. With a full-coverage schema and an output schema present, nothing an agent needs in order to select and call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description goes further by tying parameters to the rules they feed — 'written' to the in-writing test, 'received'/'starts' to the three-month rule, 'tenancyStart'/'history'/'lastIncrease' to the 12-month rule — giving an agent the reasoning behind each input.

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 the specific verb (check), resource (a landlord's rent increase notice) and jurisdiction (Northern Ireland, private tenancy), and enumerates exactly what is being tested: written form, three-month lead time, and the 12-month spacing rules. This clearly distinguishes it from the England, Scottish and Welsh rent-increase siblings.

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?

Explicitly scopes applicability: notices given from 1 April 2025, Northern Ireland only, private tenancy, and an explicit exclusion ('do not use it for a controlled tenancy, which has different rules'). It also states a boundary the tool will not answer ('does not judge whether the new rent is fair'), which prevents misrouted calls.

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

All Contract Lily 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?