Buildium MCP Server

list_unit_listings

Fetch Buildium unit listings with pagination support using limit and offset parameters.

Instructions

List unit listings from Buildium.

Args: limit: Maximum number of results (default: 100). offset: Offset for pagination (default: 0).

Returns: Dictionary with listings list.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the burden of conveying safety and behavior. It reasonably implies a read-only list operation and explains pagination, but it does not explicitly state that it is non-destructive or describe any error handling or other side effects.

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?

The description is compact, well-structured with Args and Returns sections, and contains no fluff. Every sentence contributes necessary information for using the tool.

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?

For a simple list operation with an output schema, the description covers the essential input and return information. However, it could be more complete by briefly explaining what a 'unit listing' is or how it differs from related resources, aiding the agent in selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description fully explains both parameters, including defaults and semantics ('Maximum number of results', 'Offset for pagination'), which the input schema lacks (coverage 0%). This adds real value beyond the structured 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?

The description uses a clear verb 'List' and specifies the resource 'unit listings' from Buildium. However, it does not distinguish this tool from similar list tools for other entities or clarify the unique nature of 'unit listings' versus rental/association units.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. The description only states what the tool does, not the conditions or contexts that make it the appropriate choice, unlike examples that explicitly name alternatives.

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

Deploy Server