Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

asset_build

Destructive

Create or continue an independent editable Blender asset by supplying asset ID, blend/GLB/DAE/preview paths, parts or trusted script, anchor, and license sources.

Instructions

Create/continue an independent editable Blender asset. Supply asset_id, new blend/glb/dae/preview paths, parts or trusted script, anchor and license sources.

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": {
      "specification": "<specification>",
      "operation_id": "<operation_id>"
    },
    "name": "asset_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYes
specificationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already flag the operation as destructive, non-idempotent and open-world, so the safety profile is covered. The description still adds value by hinting at file writes (blend/glb/dae/preview paths) and at executing a "trusted script", which signals arbitrary code runs. It does not say what an existing asset loses on rebuild, or how path collisions are handled.

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?

Two sentences, with the purpose front-loaded and the required values packed into a short list. The list is dense but readable, and there is no filler; the only inefficiency is that the field names are not tied back to the schema.

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?

An output schema exists, so return values need not be explained. Even so, for a destructive, non-idempotent build tool whose only described parameter is an open-ended specification object, the description leaves too much out: how to retry using operation_id, what happens when an asset_id already exists, and when to use this tool versus the native-job siblings.

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?

With 0% schema coverage, the description has to carry the field semantics, and it does list the names an agent is expected to put inside the specification object: asset_id, output paths, parts or the trusted script, anchor and license sources. It never says how these map onto the specification object, and it never mentions operation_id, even though both properties are required.

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 concrete verb plus resource: "Create/continue an independent editable Blender asset." That clearly separates it from the SketchUp siblings, which all carry a sketchup_ prefix. The "Create/continue" phrasing muddies whether this starts a new asset or resumes an existing one, so it stops short of a 5.

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 statement of when to pick this tool over other build or export paths, and no prerequisites such as needing a project or authority link first. The word "independent" hints at a scoping rule but never explains it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.