buildium-mcp

Buildium List Lease Transactions

buildium_list_lease_transactions

Read-onlyIdempotent

Retrieve posted charges and payments for a lease to review its financial activity. Use all_pages for accurate totals and count_only for transaction counts.

Instructions

List financial transactions (posted charges and payments) for a lease.

For the lease's recurring rent amount use buildium_list_leases instead — it is already on every row under AccountDetails.Rent.

Set all_pages=true when totalling a ledger, and count_only=true to learn only how many transactions there are.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Records per page, 1-1000.
`fields`	No	Keep only these top-level fields in each record, e.g. ["Id", "Name"]. Buildium records are large and carry tax IDs and addresses you may not need.
`offset`	No	How many records to skip. Use next_offset from the previous page.
`lease_id`	Yes	The lease's ID.
`all_pages`	No	Follow pagination and return the records, up to 1000. Use it for totals and other aggregates; a figure from one page is wrong whenever there is more than one page.
`count_only`	No	Follow every page, up to 100,000 records, and return only how many there are. Use it for "how many" questions.
`exclude_fixtures`	No	Leave out test records, whose names start with the fixture prefix (see buildium_health). When any are present the response says so either way.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.2.1Sep 24, 2026

addedInput schema / properties / all_pages / description

Added value: +"Follow pagination and return the records, up to 1000. Use it for totals and other aggregates; a figure from one page is wrong whenever there is more than one page."

addedInput schema / properties / count_only / description

Added value: +"Follow every page, up to 100,000 records, and return only how many there are. Use it for \"how many\" questions."

addedInput schema / properties / exclude_fixtures / description

Added value: +"Leave out test records, whose names start with the fixture prefix (see buildium_health). When any are present the response says so either way."

addedInput schema / properties / fields / description

Added value: +"Keep only these top-level fields in each record, e.g. [\"Id\", \"Name\"]. Buildium records are large and carry tax IDs and addresses you may not need."

addedInput schema / properties / lease_id / description
```
Added value: +"The lease's ID."
```
addedInput schema / properties / limit / description
```
Added value: +"Records per page, 1-1000."
```

addedInput schema / properties / offset / description

Added value: +"How many records to skip. Use next_offset from the previous page."

Changed1 schema field changedv0.2.0Sep 23, 2026
- addedInput schema / properties / count_only
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
First observedv0.1.0Sep 17, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description need not repeat those. It adds useful behavioral context by defining the result as posted charges and payments, and by relating pagination modes to user intent. There is no contradiction with annotations.

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?

Three short sentences: purpose first, then sibling routing, then pagination guidance. Every sentence earns its place, and the most important scoping information is front-loaded.

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?

With a rich output schema, detailed parameter descriptions, and strong annotations, the description covers the key decision points an agent needs: what this endpoint returns, when to use a sibling instead, and how to choose between all_pages and count_only. Nothing essential is missing for correct invocation.

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 description coverage is 100%, so the schema already documents each parameter. The description adds value by explaining the practical difference between all_pages and count_only, and by warning against using a single page for totals. This goes beyond the baseline without needing to restate the schema.

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?

The description opens with a specific verb and resource: 'List financial transactions (posted charges and payments) for a lease.' It clarifies what kind of records are returned and distinguishes itself from the sibling buildium_list_leases by explicitly noting that recurring rent belongs to that other tool.

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?

The description directly states when to prefer buildium_list_leases instead (recurring rent amount) and provides concrete conditions for all_pages (totalling a ledger) and count_only (learning only how many transactions exist). This is explicit routing guidance with minimal ambiguity.

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