Skip to main content
Glama

Binyan.im · בניינים

Update tenant

update_tenant
Destructive

Replace the tenant contact on an apartment. This overwrites the current tenant.

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": {
      "buildingId": "<buildingId>",
      "apartmentId": "<apartmentId>"
    },
    "name": "update_tenant"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildingIdYes
apartmentIdYes
tenantEmailNo
tenantPhoneNo
tenantLastNameNo
tenantFirstNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces this with "overwrites the current tenant," which is useful corroboration. However it never states whether omitted fields are cleared or preserved, whether an empty tenantEmail unassigns the tenant, or what happens to the previous tenant's history — the details that matter most for a replace operation.

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?

Two short sentences with the destructive effect placed in the second position for emphasis; no filler. Slight redundancy between "Replace the tenant contact" and "overwrites the current tenant," but it earns its brevity.

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 6-parameter destructive mutation with no output schema and no parameter documentation, the description is under-specified: an agent cannot tell whether it is performing a full replacement or a partial update, nor which of the optional fields will be wiped. That ambiguity is material for a write tool.

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 description coverage is 0% across 6 parameters and the description adds essentially nothing: it alludes to "tenant contact" but never explains that buildingId/apartmentId are required identifiers, that tenantEmail accepts an empty string to clear, or how the name/phone fields behave. It does not compensate for the coverage gap.

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?

Uses a specific verb ("Replace") and names the resource ("tenant contact on an apartment"), so an agent knows this changes tenant details on a single apartment. It stops short of distinguishing it from sibling update_* tools or clarifying whether non-contact tenant fields are touched.

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

Usage Guidelines3/5

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

Implies usage (when you need a different tenant contact on an apartment) but gives no explicit when-to-use vs alternatives, no prerequisites, and no warnings about the destructive replace despite destructiveHint being set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources