buildium-mcp

Buildium Lease Roster

buildium_lease_roster

Read-onlyIdempotent

List tenants on each lease and count co-tenants. Avoids Buildium's missing lease-tenant filter by inverting tenant records.

Instructions

Who is on which lease — the lease-to-tenant join, done in one call.

Use this for any "who lives in / who is on lease X" question, and for counting co-tenants.

Buildium makes this awkward: the lease list does not reliably populate tenant names, and the tenant endpoint has no lease filter — so answering it directly means pulling every lease one at a time. Tenant records do carry their lease membership, so this reads them and inverts the mapping locally.

Every matching tenant is read, following pagination; complete says whether that covered them all. Above 300 leases only the counts are returned (multi_tenant_lease_count and friends); narrow with property_id or lease_id for lease ids and names.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size used while reading tenants, 1-1000. It does not cap the roster.
`lease_id`	No	Only this lease. Reads just that lease's unit: two requests however large the account.
`property_id`	No	Only this rental property.
`lease_status`	No	Active, Past or Future: only tenants with a lease term in that state. Active is usually what "who lives here" means, and skips years of past tenants.
`exclude_fixtures`	No	Leave out tenants created by test tooling, 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.

Changed5 schema fields changedv0.2.1Sep 24, 2026

addedInput schema / properties / exclude_fixtures / description

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

addedInput schema / properties / lease_id / description

Added value: +"Only this lease. Reads just that lease's unit: two requests however large the account."

addedInput schema / properties / lease_status / description

Added value: +"Active, Past or Future: only tenants with a lease term in that state. Active is usually what \"who lives here\" means, and skips years of past tenants."

addedInput schema / properties / limit / description

Added value: +"Page size used while reading tenants, 1-1000. It does not cap the roster."

addedInput schema / properties / property_id / description
```
Added value: +"Only this rental property."
```

Changed2 schema fields changedv0.2.0Sep 23, 2026

addedInput schema / properties / lease_status

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

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

First observedv0.1.0Sep 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description goes beyond these by disclosing pagination behavior: 'Every matching tenant is read, following pagination; `complete` says whether that covered them all.' It also reveals a threshold: 'Above 300 leases only the counts are returned (multi_tenant_lease_count and friends); narrow with property_id or lease_id for lease ids and names.' This is valuable behavioral context that the annotations alone do not provide, and it does not contradict them.

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?

The description is a single paragraph of about 120 words. It is front-loaded with the core purpose and usage, then provides background on Buildium's limitations, and finally describes behavior. Every sentence carries information; there is no fluff. However, it is slightly longer than necessary—the Buildium explanation, while useful, could be condensed. Overall, it is well-structured and concise enough for its complexity.

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?

The tool has an output schema (though not shown here), and the description covers key output details like the `complete` flag and the count fields (multi_tenant_lease_count). It also explains edge cases (300-lease threshold, fixture exclusion) and how parameters affect behavior. Given the tool's complexity (joining leases and tenants, pagination, limits), the description is complete enough for an agent to understand what to expect and how to call it correctly. No important gaps are apparent.

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 coverage is 100%, so the baseline is 3. The description mentions 'narrow with property_id or lease_id' but this is already stated in the schema descriptions. It adds no new parameter meaning beyond what the schema provides. For example, the `limit` parameter's schema already explains it is a page size and does not cap the roster; the description repeats this implicitly but does not add extra detail. Thus, the description does not compensate for any gap because there is none, but it also does not add value beyond 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 precise statement of what the tool does: 'Who is on which lease — the lease-to-tenant join, done in one call.' It clearly identifies the resource (leases and tenants) and the operation (joining them). It also distinguishes itself from siblings by explicitly stating its intended use: 'Use this for any "who lives in / who is on lease X" question, and for counting co-tenants.' This is a specific verb+resource and differentiates from tools like buildium_list_leases or buildium_list_tenants.

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 gives explicit when-to-use guidance: 'Use this for any "who lives in / who is on lease X" question, and for counting co-tenants.' It also explains why it is needed (Buildium's limitations: lease list doesn't reliably populate tenant names, tenant endpoint has no lease filter). It further instructs on narrowing results: 'narrow with property_id or lease_id for lease ids and names.' This provides clear context for when to use this tool versus alternatives, even if it doesn't name a specific sibling to avoid.

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