Buildium MCP Server

update_applicant

Update an existing applicant's details in Buildium by passing their applicant ID and the updated data. This changes their record to match new information.

Instructions

Update an existing applicant.

Args: applicant_id: The applicant ID. applicant_data: Updated applicant data dictionary.

Returns: Updated applicant 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": {
      "applicant_id": "<applicant_id>",
      "applicant_data": "<applicant_data>"
    },
    "name": "update_applicant"
  }
}

Input Schema

Name	Required	Description	Default
`applicant_id`	Yes
`applicant_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.7/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only says 'update' and 'returns updated details,' but doesn't disclose partial vs full replacement, validation rules, permissions, or 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.

Conciseness4/5

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

The description is compact and logically formatted with Args/Returns sections. It is concise, though could afford a bit more detail without becoming verbose.

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?

Despite an output schema, the tool is incomplete without update semantics and usage context. The nested applicant_data parameter is undefined, making it hard to construct a valid update payload.

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?

Schema coverage is 0%, so description must compensate. It identifies applicant_id and applicant_data as a dictionary, but doesn't specify which fields are updatable or the exact meaning of the data dictionary.

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?

Clearly states it updates an existing applicant with a specific verb and resource. However, it doesn't distinguish from sibling update tools like update_application or update_applicant_group, but the applicant resource is unambiguous.

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 on when to use this tool versus create_applicant or other update tools. No mention of prerequisites, context, or exclusions.

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

Deploy Server