Skip to main content
Glama

Create asset

create_asset

Create a new asset. Requires assets:write scope. IMPORTANT - Location hierarchy: always resolve top-down by calling list_sites first, then list_buildings filtered by site_id, then list_locations filtered by building_id. Provide all three IDs (site_id, building_id, location_id) explicitly. System hierarchy: similarly resolve via list_system_classes → list_system_groups → list_systems.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAsset name (required)
modelNoModel name/number
site_idNoSite ID - resolve first via list_sites
asset_idNoCustom asset identifier (unique per tenant) - resolve via list_assets
quantityNoQuantity
image_urlNoImage URL
status_idNoStatus ID from list_asset_statuses. The status with system_key archived archives the asset; any other status restores it.
system_idNoSystem ID - resolve last via list_systems filtered by system_group_id
meter_unitNoMeter unit (km, miles, hours, cycles)
building_idNoBuilding ID - resolve second via list_buildings filtered by site_id
descriptionNoDescription
location_idNoLocation ID - resolve last via list_locations filtered by building_id
risk_factorNoRisk factor (CRITICAL, HIGH, MEDIUM, LOW)
asset_type_idNoAsset type ID (from asset_types) - resolve via list_asset_types
purchase_costNoPurchase cost
purchase_dateNoPurchase date (ISO 8601)
safety_impactNoSafety impact level (LOW, MEDIUM, HIGH, CRITICAL)
salvage_valueNoSalvage value
serial_numberNoSerial number
cost_per_sq_ftNoCost per square foot
service_impactNoService impact level (LOW, MEDIUM, HIGH, CRITICAL)
archived_reasonNoWhy the asset is archived. Kept only while it is archived.
condition_scoreNoCondition score (0-100)
manufacturer_idNoManufacturer ID (from manufacturers) - resolve via list_manufacturers
system_class_idNoSystem class ID - resolve first via list_system_classes
system_group_idNoSystem group ID - resolve second via list_system_groups filtered by system_class_id
unit_of_measureNoUnit of measure
regulatory_impactNoRegulatory impact level (LOW, MEDIUM, HIGH, CRITICAL)
replacement_valueNoCost to replace this asset today, in current dollars. Distinct from purchase_cost, which is what was paid and is the depreciation basis.
reputation_impactNoReputation impact level (LOW, MEDIUM, HIGH, CRITICAL)
environmental_impactNoEnvironmental impact level (LOW, MEDIUM, HIGH, CRITICAL)
current_meter_readingNoCurrent meter/odometer reading
last_maintenance_dateNoLast maintenance date (ISO 8601)
unit_replacement_valueNoUnit replacement value
expected_lifetime_yearsNoExpected lifetime in years
salvage_value_percentageNoSalvage value percentage (0-100)
likelihood_of_failure_scoreNoLikelihood of failure score, 1-5. Derived from condition_score unless set: setting it makes it a manual value that condition changes no longer replace; send null to return it to derivation.
consequence_of_failure_scoreNoConsequence of failure score, 1-5. Setting it makes it a manual value that a system change no longer replaces; send null to return it to the default from its system.
replacement_value_reviewed_onNoDate replacement_value was last confirmed (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / asset_id / description
      Previous value: -"Custom asset identifier (unique per tenant)"New value: +"Custom asset identifier (unique per tenant) - resolve via list_assets"
    • changedInput schema / properties / asset_type_id / description
      Previous value: -"Asset type ID (from asset_types)"New value: +"Asset type ID (from asset_types) - resolve via list_asset_types"
    • changedInput schema / properties / manufacturer_id / description
      Previous value: -"Manufacturer ID (from manufacturers)"New value: +"Manufacturer ID (from manufacturers) - resolve via list_manufacturers"
  2. Changed5 schema fields changed
    • addedInput schema / properties / archived_reason
      Added value: +{
      +  "description": "Why the asset is archived. Kept only while it is archived.",
      +  "enum": [
      +    "replaced",
      +    "disposed",
      +    "sold",
      +    "transferred",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / status_id / description
      Previous value: -"Status identifier"New value: +"Status ID from list_asset_statuses. The status with system_key archived archives the asset; any other status restores it."
    • addedInput schema / properties / status_id / format
      Added value: +"uuid"
    • removedInput schema / properties / status_id / maxLength
      Removed value: -100
    • addedInput schema / properties / status_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 / properties / consequence_of_failure_score / description
      Previous value: -"Consequence of failure score"New value: +"Consequence of failure score, 1-5. Setting it makes it a manual value that a system change no longer replaces; send null to return it to the default from its system."
    • changedInput schema / properties / consequence_of_failure_score / maximum
      Previous value: -9007199254740991New value: +5
    • changedInput schema / properties / consequence_of_failure_score / minimum
      Previous value: -0New value: +1
    • changedInput schema / properties / likelihood_of_failure_score / description
      Previous value: -"Likelihood of failure score"New value: +"Likelihood of failure score, 1-5. Derived from condition_score unless set: setting it makes it a manual value that condition changes no longer replace; send null to return it to derivation."
    • changedInput schema / properties / likelihood_of_failure_score / maximum
      Previous value: -9007199254740991New value: +5
    • changedInput schema / properties / likelihood_of_failure_score / minimum
      Previous value: -0New value: +1
  4. Changed12 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 / asset_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 / building_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 / consequence_of_failure_score / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / likelihood_of_failure_score / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / location_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 / manufacturer_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 / 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})$"
    • addedInput schema / properties / system_class_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 / system_group_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 / system_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. Changed12 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 / asset_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 / building_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 / consequence_of_failure_score / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / likelihood_of_failure_score / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / location_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 / manufacturer_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 / 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})$"
    • removedInput schema / properties / system_class_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 / system_group_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 / system_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})$"
  6. Changed12 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 / asset_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 / building_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 / consequence_of_failure_score / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / likelihood_of_failure_score / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / location_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 / manufacturer_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 / 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})$"
    • addedInput schema / properties / system_class_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 / system_group_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 / system_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})$"
  7. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (not read-only, not destructive, not idempotent), so this is a lower bar; the description adds genuine value by naming the required 'assets:write' scope, which an agent cannot get from the schema or hints. It does not disclose failure behavior or what the response contains, but the auth disclosure is a meaningful addition.

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?

Front-loaded with the action then the two hierarchy workflows, using caps and arrows for scannability. Some of the hierarchy resolution text is repeated in the per-parameter schema descriptions, so it is not maximally efficient, but it is short for a 39-parameter tool.

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?

For a 39-parameter mutation with no output schema, the description covers the hardest part of a correct call (dependency resolution order) and the auth prerequisite. It omits idempotency/uniqueness expectations for asset_id and any note about the created record's return shape, but nothing essential to making the call is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds real semantics beyond the schema by stating all three location IDs should be supplied explicitly (only 'name' is formally required) and by prescribing the exact resolution order and filter keys that link site_id/building_id/location_id and the system IDs.

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 ('Create a new asset') with clear intent, and immediately scopes it with an auth requirement. It does not, however, differentiate itself from close siblings such as create_infrastructure_asset or bulk_create, which an agent must infer from the names alone.

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?

Gives explicit, actionable prerequisites: resolve location hierarchy top-down via list_sites → list_buildings → list_locations, and system hierarchy via list_system_classes → list_system_groups → list_systems, with the required filter key for each step. It stops short of saying when to prefer this over bulk_create or create_infrastructure_asset.

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