lendlord-mcp

Compliance overview

compliance_overview

Read-only

Track upcoming and overdue compliance expiry dates across a landlord portfolio, sorted soonest first, and flag items due within a set number of days.

Instructions

Upcoming and overdue expiry dates across the portfolio (EPC, insurance, gas safety, EICR, mortgage rate expiry, …), sorted soonest first.

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

Input Schema

Name	Required	Description	Default
`withinDays`	No	Flag items expiring within this many days

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare a read-only, open-world operation. The description adds useful behavioral context: it covers both upcoming and overdue items across the entire portfolio and specifies soonest-first ordering. It does not state permissions or result-shape limitations, but the annotation coverage lowers the burden.

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?

The definition is a single front-loaded sentence with no wasted words. The parenthetical category examples and sort order are immediately useful and do not distract from the core purpose.

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?

For a read-only overview tool with no output schema, the description sufficiently states what is returned: expiry items across compliance categories, sorted soonest first. It does not specify returned fields such as property identifiers or exact dates, but the core return content is clear enough to call the tool correctly.

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 description coverage is 100%, so the single withinDays parameter is already fully documented in the schema. The description adds no extra parameter meaning beyond what the schema provides, which meets the baseline for fully covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource and scope: upcoming and overdue expiry dates across the portfolio, with concrete compliance categories and sort order. It does not explicitly differentiate from any sibling tool, but the sibling list contains no obvious competing compliance overview tool.

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?

Usage is implied by the compliance and expiry context, but the description gives no explicit when-to-use or when-not-to-use guidance, and it does not name any alternative sibling tool.

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