buildium-mcp

Buildium List Work Orders

buildium_list_work_orders

Read-onlyIdempotent

List maintenance work orders from Buildium, with options to count records, fetch all pages, and exclude test fixtures.

Instructions

List work orders (maintenance jobs).

To count, use count_only; for totals, all_pages.

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.
`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.

Changed6 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 / 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/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds little behavioral detail beyond the schema: it restates count and totals guidance already present in parameter descriptions. It does not contradict annotations, and no additional side-effect disclosure is needed for a read-only tool.

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 extremely compact: one sentence establishes purpose, and a second sentence highlights the two parameter modes that matter most. There is no filler or redundant detail; every word earns its place.

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?

The description is sufficient for this tool given the rich input schema, output schema, and annotations. It names the resource and the key usage nuances. It could explicitly mention when to prefer a sibling tool, but the tool name and schema already carry most of the contextual burden.

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 the baseline is 3. The description's parameter-related advice ("use count_only", "all_pages") restates what the schema already says rather than adding new meaning. It adds no parameter semantics beyond the structured 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 states a specific verb and resource: "List work orders (maintenance jobs)." This clearly identifies what the tool does and distinguishes it from sibling list tools like buildium_list_rentals and buildium_list_units by naming the entity. The parenthetical synonym adds helpful clarity.

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

Usage Guidelines4/5

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

The description provides clear guidance on the two main usage modes: "To count, use count_only; for totals, all_pages." This orients the agent toward the right parameters for the right questions. It does not explicitly compare this tool to alternatives, but the resource-specific name makes the primary use case obvious.

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