Buildium MCP Server

create_vendor

Create a vendor in Buildium by submitting vendor data. Streamline vendor management with a direct integration that adds new vendors to your property management system.

Instructions

Create a new vendor.

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": {
      "vendor_data": "<vendor_data>"
    },
    "name": "create_vendor"
  }
}

Input Schema

Name	Required	Description	Default
`vendor_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.6/5.0

Behavior1/5

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

No annotations are provided, and the description only says 'Create a new vendor.' It discloses no side effects, required permissions, validation behavior, return values, or edge cases. This is entirely opaque for a create operation.

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 a single, concise sentence that gets straight to the point. It is appropriately sized and front-loaded, with no unnecessary words or repetition.

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

Completeness1/5

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

Given the tool has an open-ended vendor_data object and no annotations, the description is far too minimal. It does not explain what a vendor is, what data is required, or what the tool returns. An agent would be unable to correctly invoke it beyond the obvious create action.

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 input schema has a single parameter 'vendor_data' with no description and 0% schema coverage. The description does not mention this parameter or any fields it should contain. It completely fails to compensate for the lack of schema documentation.

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 clearly states the verb 'create' and the resource 'vendor', making it obvious the tool creates a new vendor. It distinguishes from sibling tools like list_vendors, get_vendor, and update_vendor by specifying the create action on the vendor entity.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that it should be used for adding a new vendor, nor does it reference any sibling tools or exclusions. The usage is only implied by the name and description.

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

Deploy Server