Skip to main content
Glama

Binyan.im · בניינים

Add apartment

add_apartment

Add an apartment to a building in this ועד בית account.

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>",
      "number": "<number>",
      "floor": "<floor>",
      "sizeSqM": "<sizeSqM>"
    },
    "name": "add_apartment"
  }
}

Input Schema

NameRequiredDescriptionDefault
floorYes
numberYes
sizeSqMYes
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that the description adds nothing: no statement about validation failures, whether the apartment number must be unique within the building, what happens if buildingId is unknown, or what the call returns.

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?

A single well-formed sentence with no filler and the resource front-loaded. It is concise but under-specified, so brevity comes at the cost of the guidance a caller needs.

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?

This is a four-required-parameter write operation with no output schema and zero parameter documentation in the schema. The description supplies none of the missing pieces (building prerequisite, field meanings, likely errors), so it is not sufficient for confident invocation.

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% for 4 required parameters, so the description must carry the load and it does not. It hints that one parameter references a building, but says nothing about what 'number' means (unit label vs numeric), why 'floor' must be >= 0, or the unit/meaning of sizeSqM.

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?

States a specific verb and resource ('Add an apartment to a building') and scopes it to an account, so it is clearly a create-mutation rather than a read like list_apartments. It stops short of naming any sibling or explaining how it differs from create_building/update_tenant, but the verb+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 when-to-use or when-not-to-use guidance: the description never says the referenced building must already exist (implying create_building first), nor does it mention list_apartments for checking duplicates. An agent must infer the call sequence entirely.

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