Skip to main content
Glama
mcp-123bail
by lydstyl

get_payment_summary_by_landlord

Retrieve a landlord's payment summary for active leases over the last N months, showing monthly due, paid, and balance amounts per lease.

Instructions

Payment summary over the last N months for the active leases of a landlord (per-lease monthly due/paid/balance)

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": {
      "landlord": "<landlord>"
    },
    "name": "get_payment_summary_by_landlord"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoNumber of months to summarize (default 3)
landlordYesLandlord name or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add real behavioral content — the aggregation is limited to active leases and broken down per lease as monthly due/paid/balance — but it omits whether the window includes current or future months, how inactive leases are treated, and what happens for an unknown landlord.

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 tightly packed sentence with the scope constraints front-loaded and a parenthetical that conveys the return shape. Slightly dense, but every clause carries information and nothing is redundant.

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?

There is no output schema, so the description responsibly sketches the result shape (per-lease monthly due/paid/balance), and the two-parameter schema is fully self-describing. For a read-only summary tool this is largely sufficient, with only edge-case behavior left unstated.

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 (months with default/min/max, landlord name-or-ID) are already fully documented. The description restates the N-month window and landlord scoping without adding format or resolution detail beyond the schema, so the baseline of 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?

The description states a specific resource (payment summary) with explicit scope: the last N months, active leases only, for a landlord. That verb+resource+scope combination differs clearly from sibling reads like get_properties_by_landlord or get_tenants_by_landlord, though no sibling is named explicitly.

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 through the scoping constraints (landlord-scoped, active leases, N-month window), but there is no explicit when-to-use or when-not guidance and no alternative tool is named. An agent must infer that this is the aggregate-reporting tool versus per-record tools.

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