lendlord-mcp

List properties

list_properties

Read-only

Retrieve portfolio properties with address, postcode, value, rent, and mortgage figures. Filter by address/postcode text or status to focus on active records.

Instructions

All properties in the portfolio with key figures (address, postcode, value, rent, mortgage). Optionally filter by free text matched against address/postcode.

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

Input Schema

Name	Required	Description	Default
`search`	No	Case-insensitive text to match in address or postcode
`status`	No	Filter by status, e.g. "active"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results include key figures, but says nothing about pagination, result limits, or auth, so it adds only modest context beyond the annotations.

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 tight sentences with the core listing behavior front-loaded and the filter noted second. No filler, though the parenthetical field list could be trimmed since it mirrors the return data.

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

Completeness3/5

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

With no output schema, the description does list the fields returned, which helps. But it omits pagination/result-size behavior and never mentions the status filter, so an agent is left guessing about result scope.

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 both parameters are already documented in the schema. The description restates the search behavior ('matched against address/postcode') but adds nothing for the status parameter, so the baseline 3 applies.

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?

States a clear verb (list) and resource (properties) and even enumerates the returned key figures (address, postcode, value, rent, mortgage). It reads as a portfolio-wide listing, but it does not differentiate itself from siblings like find_property or get_property, which an agent must otherwise infer.

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?

The description implies usage via 'Optionally filter by free text matched against address/postcode,' giving the agent a sense of when to use the search parameter. However, it gives no explicit when-to-use versus find_property/get_property, and never mentions the status filter or any exclusion.

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