Skip to main content
Glama

Create asset placement

create_asset_placement

Place an asset on a floorplan at the given (x, y) coordinate (normalized 0-1, origin top-left). UPSERTS by asset_id - an asset can have at most ONE placement globally, so calling this again just moves the pin. Use bulk_create with resource="asset-placements" to place many assets at once. Requires asset_placements:write scope.

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": {
      "asset_id": "<asset_id>",
      "floorplan_id": "<floorplan_id>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "create_asset_placement"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesNormalized x coordinate (0=left, 1=right)
yYesNormalized y coordinate (0=top, 1=bottom)
sourceNo"manual" (default) or "ai" for AI-placed
asset_idYesAsset to place (resolve via list_assets)
region_idNoRegion the pin sits inside. Not inferred from the pin position: set it if the pin belongs to a region. - resolve via list_floorplan_regions
floorplan_idYesTarget floorplan (resolve via list_floorplans)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / region_id / description
      Previous value: -"Region the pin sits inside. Not inferred from the pin position: set it if the pin belongs to a region."New value: +"Region the pin sits inside. Not inferred from the pin position: set it if the pin belongs to a region. - resolve via list_floorplan_regions"
  2. Changed1 schema field changed
    • changedInput schema / properties / region_id / description
      Previous value: -"Optional region the pin sits inside (usually auto-inferred)"New value: +"Region the pin sits inside. Not inferred from the pin position: set it if the pin belongs to a region."
  3. Changed5 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_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 / floorplan_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 / region_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})$"
  4. Changed5 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_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 / floorplan_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 / region_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})$"
  5. Changed5 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_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 / floorplan_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 / region_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})$"
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description contributes real behavioral context beyond the annotations: it is an UPSERT keyed on asset_id, so repeat calls move rather than duplicate the pin — a non-obvious trait given a create_* name. It also discloses the write-scope requirement. Note a mild tension with idempotentHint=false, since upsert-by-key semantics normally converge on repeat calls; this looks like an annotation nuance rather than a reversal of the described behavior.

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?

Four short sentences, all high-value: placement semantics first, then upsert behavior, then the bulk alternative, then the auth requirement. No filler and nothing important buried at the end.

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?

Covers required inputs, uniqueness semantics, bulk alternative, and scope for a mutation tool with no output schema. The only gap is that it never indicates what comes back (e.g., the created placement id) or whether the returned record should be retained for later update/delete calls.

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%, including coordinate normalization, origin, the source enum, and resolution hints for asset_id/floorplan_id/region_id. The description restates the 0-1/top-left convention but adds nothing about the optional region_id inference rule, so it does not exceed the schema baseline.

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 concrete verb and resource ('Place an asset on a floorplan at the given (x, y) coordinate') plus the key scope constraint: exactly one placement per asset globally. An agent can distinguish this from update_asset_placement and delete_asset_placement from the sentence alone.

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

Usage Guidelines5/5

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

Explicitly names the alternative ('Use bulk_create with resource="asset-placements" to place many assets at once') and the condition that selects it, and states the required asset_placements:write scope. Both when-to-use and prerequisite information are present.

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