Skip to main content
Glama

Feature Instantiate

feature_instantiate
Destructive

Stamps a registered feature template onto a host body at named reference geometry, validating and resolving references against current host geometry before building.

Instructions

Stamp a registered FEATURE TEMPLATE onto a host body at reference geometry supplied BY NAME (PowerCopy/UDF, issue #139) — e.g. a mounting_boss onto a published seat frame, or a bolt_pattern onto an f_ face tag. Validates {refs, inputs} at the door, resolves each reference against the host's CURRENT geometry (an f_ tag / interface name that doesn't resolve fails loudly), then runs the deterministic build — geometry + publish_interface + declare_intent.

template: registered template name (feature_list to browse). host: the handle of the body to stamp onto. refs: reference inputs by name — an interface name, an f_/e_ tag, or a literal {origin, z_axis?, x_axis?} frame, per the template's declared ref kinds. inputs: scalar parameters (typed + unit-bearing + range-checked).

Returns {template, schema, host, refs, inputs, handle, name, interfaces, intent}.

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": {
      "template": "<template>",
      "host": "<host>"
    },
    "name": "feature_instantiate"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
refsNo
inputsNo
templateYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructive=true, readOnly=false, but the description adds real value: upfront {refs,inputs} validation, loud failure when an f_ tag/interface doesn't resolve against current geometry, and side effects beyond geometry (publish_interface + declare_intent). It doesn't state permission requirements or exactly what pre-existing geometry is overwritten, so not a 5.

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 purpose and examples, then systematically handles params and return shape. Dense but every line earns its place; only the annotated param breakdown repeats the schema titles, slightly redundant.

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?

No output schema, but the description explicitly documents the return object ({template, schema, host, refs, inputs, handle, name, interfaces, intent}), plus validation and side-effect behavior. Complete for calling correctly; minor gaps on permissions/reversibility remain.

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 only 20% (only workspace documented), so the description carries the burden — and it does, explaining template (browse via feature_list), host (body handle), refs (interface name, f_/e_ tag, or literal frame per declared ref kind), and inputs (typed, unit-bearing, range-checked). Only workspace is left unexplained, hence not a 5.

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 (stamp/instantiate) and resource (registered feature template onto host body), with concrete examples (mounting_boss onto seat frame, bolt_pattern onto f_ face tag). An agent can distinguish this from feature_list/feature_validate/family_materialize without opening a schema.

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?

Points to feature_list to browse templates and gives example pairings, implicitly establishing the discovery-then-instantiate workflow. It does not explicitly state when to prefer this over siblings like family_materialize, so it stops short of full when/when-not routing.

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

Deploy Server

Other Tools