lendlord-mcp

List communications

list_communications

Read-only

Retrieve tenant and landlord communications, including maintenance reports, newest first. Filter by property or type and paginate using limit and skip.

Instructions

Maintenance reports and other tenant/landlord communications, newest first. Fetches Lendlord's 100-item pages as needed up to limit (max 1000); continue with skip = nextSkip while hasMore is true.

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_communications"
  }
}

Input Schema

Name	Required	Description
`skip`	No
`type`	No	e.g. "maintenanceReport"
`limit`	No
`propertyId`	No	Only communications for this property

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Oct 15, 2026

changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +1000
```

addedInput schema / properties / propertyId

Added value: +{
+  "description": "Only communications for this property",
+  "type": "string"
+}

First observedv0.1.1Oct 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds non-obvious behavior the schema does not: upstream paging happens in 100-item pages, the effective ceiling is 1000, and the response carries hasMore/nextSkip continuation state. That is real behavioral disclosure (no output schema exists), though error/rate-limit behavior is unstated.

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, no filler. The first front-loads what the tool returns and in what order; the second carries the pagination mechanics. Every clause conveys actionable information.

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 no output schema, the description must cover return behavior, and it does supply the paging model and continuation fields that an agent needs to loop correctly. It is slightly incomplete in that the shape of individual communication records and the hasMore/nextSkip field names' location (top-level vs nested) are not spelled out, but nothing essential to invoking it 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 50% (type and propertyId documented, skip and limit not). The description compensates well: it defines limit's ceiling ('max 1000'), explains how skip is derived from the response ('skip = nextSkip'), and its example of maintenance reports clarifies the intended type value. Only propertyId filtering is left entirely to the schema.

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 specific verb (list) and resource (communications), and goes further by defining what counts as a communication: 'Maintenance reports and other tenant/landlord communications', plus the sort order (newest first). It does not name the related single-item or mutation siblings (get_communication, log_communication, update_communication), so differentiation is inferred from the noun rather than stated.

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 gives concrete continuation instructions ('continue with skip = nextSkip while hasMore is true'), which tells the agent how to iterate but not when to choose this tool over get_communication, list_documents, or log_communication. No explicit when-to-use vs when-not context is provided beyond the resource scope.

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