Skip to main content
Glama

Create building

create_building

Create a new building. Requires buildings:write scope. latitude and longitude place the building on the map and must be sent together - one without the other is rejected.

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

Input Schema

NameRequiredDescriptionDefault
nameYesBuilding name (required)
typeNoBuilding type label
floorsNoNumber of floors
site_idYesSite ID (required) - resolve via list_sites
latitudeNoWGS 84 latitude of the building, in decimal degrees. Must be sent together with longitude.
area_sqftNoArea in square feet
longitudeNoWGS 84 longitude of the building, in decimal degrees. Must be sent together with latitude.
year_builtNoYear the building was constructed
building_type_idNoBuilding type ID (from building_types) - resolve via list_building_types

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / building_type_id / description
      Previous value: -"Building type ID (from building_types)"New value: +"Building type ID (from building_types) - resolve via list_building_types"
    • changedInput schema / properties / site_id / description
      Previous value: -"Site ID (required)"New value: +"Site ID (required) - resolve via list_sites"
  2. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / building_type_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • addedInput schema / properties / floors / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / floors / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / site_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  3. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / building_type_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • removedInput schema / properties / floors / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / floors / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / site_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / building_type_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • addedInput schema / properties / floors / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / floors / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / site_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-idempotent, non-destructive. The description adds two things structured data does not: an auth scope requirement and an input validation rule ("one without the other is rejected") that would otherwise cause a failed call. It does not address duplicate-name behavior despite idempotentHint=false, but that is a modest gap against annotations that already carry the safety profile.

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?

Two sentences, no waste, and the action statement plus scope requirement lead before the coordinate caveat. Every sentence earns its place.

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

Completeness3/5

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

For a 9-parameter mutation with no output schema and no annotation covering permissions, the description covers the auth requirement and the one risky optional-parameter interaction. It omits required-field expectations and what the call returns, leaving the agent to infer the response shape from convention.

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 description coverage is 100%, so the baseline is 3. The latitude/longitude pairing constraint the description calls out is already stated verbatim in both property descriptions, so the description adds no parameter meaning beyond the schema.

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+resource ("Create a new building") that an agent can distinguish from update_building, delete_building, and create_building_type. It does not, however, differentiate itself from bulk_create or from the create_site prerequisite chain, so precision is not at the sibling-aware level.

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?

The description gives one hard prerequisite ("Requires buildings:write scope"), which implies usage context, but never says when to use create_building instead of bulk_create for many buildings, or that a site must already exist. Usage is inferable from the verb, not stated.

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