Buildium MCP Server

create_bill

Create a new bill in Buildium by providing the bill data. Simplify accounting by recording bills directly through natural language.

Instructions

Create a new bill.

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": {
      "bill_data": "<bill_data>"
    },
    "name": "create_bill"
  }
}

Input Schema

Name	Required	Description	Default
`bill_data`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the action without mentioning potential side effects, required permissions, data persistence, or validation rules. For a create (mutation) tool, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the core purpose in a single sentence. However, it is under-specified rather than efficiently informative, offering no additional context that would make the sentence 'earn its place' beyond what the tool name already conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the tool has a nested object parameter (bill_data) and an output schema, the description should clarify the expected structure or provide some context about the bill domain. It does neither, making the tool inadequate for an agent to correctly invoke without external knowledge.

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

Parameters1/5

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

The schema defines a single 'bill_data' object with no description and 0% schema description coverage, but the tool description does not mention or clarify this parameter at all. The description provides no meaning beyond the schema field name, so the agent has no insight into what should be included in bill_data.

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 clearly states the action ('Create') and resource ('a new bill'), which distinguishes it from sibling tools like list_bills, get_bill, and update_bill. However, it lacks any elaboration on what a 'bill' represents or how this creation differs from other create_* tools, so it stops short of full clarity.

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?

No guidance is provided on when to use this tool versus alternatives such as update_bill or create_bill_payment. The description does not mention prerequisites, intended use cases, or any exclusion criteria, leaving the agent to infer usage from the name alone.

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

Deploy Server