Skip to main content
Glama

Binyan.im · בניינים

Back up building

backup_building
Read-only

Exports the full building data as JSON that can be restored from the website settings page. Use before bulk changes. The response is the exact backup JSON the website restore accepts and can be large.

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>"
    },
    "name": "backup_building"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior the annotations do not: the response is the exact JSON the website restore accepts, and it 'can be large', which warns the agent about payload size. Auth requirements and any rate limits remain unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short sentences, front-loaded with what the tool does, followed by when to use it and a size warning. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately characterizes the return value as a full backup JSON blob that may be large. Combined with read-only annotations and a single trivial parameter, an agent has enough to invoke it correctly; only authentication or failure-mode behavior is missing.

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

Parameters3/5

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

Schema coverage is 0% and the single buildingId parameter is never described in prose. However, the parameter name is self-explanatory and required, so the gap is minor; a 3 reflects a self-evident ID with no added meaning from the description.

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?

States a specific verb ('Exports') and resource ('the full building data') plus the output format (JSON restorable from the website settings page). No sibling tool performs backups, so there is no ambiguity to resolve among the listed alternatives.

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

Usage Guidelines4/5

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

'Use before bulk changes' gives an explicit triggering condition for calling the tool. It does not state when-not to use it or name an alternative, but no sibling offers comparable functionality, so the practical guidance is clear.

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