Skip to main content
Glama
Sign In
Buildium MCP Server

Buildium MCP Server

by luthersystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_rental

Create a new rental property by providing rental data, and receive the details of the created rental.

Instructions

Create a new rental property.

Args: rental_data: Rental property data dictionary with required fields.

Returns: Created rental property details.

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": {
      "rental_data": "<rental_data>"
    },
    "name": "create_rental"
  }
}

Input Schema

NameRequiredDescriptionDefault
rental_dataYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior1/5

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

With no annotations, the description carries the full burden, but it merely restates the tool's name. It does not disclose permissions, validation requirements, side effects, or error behavior.

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 concise and front-loaded with purpose, using a clean Args/Returns structure. The Returns line is slightly redundant but does not harm clarity.

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?

For a create operation with a single free-form object parameter, the description lacks field details, examples, or prerequisites. The output schema may cover returns, but input semantics are severely under-specified.

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

Parameters2/5

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

The description labels rental_data as a 'dictionary with required fields' but doesn't list any specific fields, leaving the agent without enough information. Schema coverage is 0% and this minimal hint does not compensate.

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 'Create a new rental property' with a specific verb and resource. This distinguishes it from siblings like update_rental, get_rental, and create_rental_unit.

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 explicit guidance on when to use this tool versus alternatives, and no mention of prerequisites or exclusions. The many related CRUD siblings make this confusion likely.

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

Deploy Server

Other Tools