Skip to main content
Glama

Binyan.im · בניינים

Create building

create_building

Create a new building for 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": {
      "name": "<name>",
      "address": "<address>"
    },
    "name": "create_building"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
addressYes
currencyNoILS
timezoneNoIANA time zone of the building, for example Asia/Jerusalem. Defaults to UTC.
duesDueDayNoDay of the month monthly dues are due, 1 to 28. Defaults to 10.

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 this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered externally. The description adds nothing beyond that: no statement about duplicate-name handling, whether defaults are applied on creation, permission requirements, or what is returned. For a creation tool the idempotency consequence (a second identical call creates a second building) is left entirely unexplained.

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 compact sentence with no filler and the verb front-loaded, which is structurally sound. However, brevity here comes at the cost of under-specification rather than serving 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?

Five parameters, two of them required, with no output schema and no behavioral detail in the description leaves the agent under-informed for a write operation. The absence of an output schema removes the need to describe returns, but nothing else fills the gap for setup fields like currency and duesDueDay.

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 only 40%, so the description should compensate, but it mentions no parameters at all. Only timezone and duesDueDay carry their own schema descriptions; name, address, and currency are undocumented in both places, and the description gives no hint about required fields or sensible values.

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?

The description states a specific verb and resource ('Create a new building'), which cleanly separates it from read siblings like list_buildings and from backup_building. The trailing scope phrase 'for this ועד בית account' is ambiguous and mixes languages but does not obscure the core action.

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?

There is no guidance on when to create a building versus alternatives such as add_apartment, backup_building, or import flows. No prerequisites, ordering, or preconditions (e.g. whether an account must already exist) are mentioned.

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