Skip to main content
Glama

OwlCAD

by com.owlcad.mcp
OverviewDiscussionsAdmin

Edit a project

edit_project
Destructive

Make a TARGETED change to one of your projects — change a parameter, move a node, add or remove one, group nodes into a boolean, create or set a variable, switch configuration. Prefer this over update_project when you are changing an existing model: it needs only the ids you are touching, not the whole tree, and it does not strand mates the way a wholesale replacement does. Read with get_project authored: true first — those are the ids this accepts. Every op must apply or the whole call is refused and nothing is written. It can also restructure: dissolve a boolean, unwrap a modifier, or turn a selection into a reusable component you place again with addInstance — which is how you build an assembly without paying for every copy against the node cap. owlcad://schema/edit-ops lists what every op requires; the schema below is a flat bag of every field any op takes.

Input Schema

NameRequiredDescriptionDefault
opsYesEdits to apply in order, each against the result of the last. Up to 40.
nameNoRename the project at the same time (optional).
versionYesThe `version` get_project reported. A mismatch means someone else changed it — re-read and retry.
projectIdYesThe project to edit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ops / items / properties / node / description
      Previous value: -"The node to insert (addNode) — same shape as a `nodes` entry: {kind, name, type|op|generatorKey, params, transform}. For kind=generator, generatorKey is one of: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock. See owlcad://schema/primitives for parameter ranges and owlcad://schema/conventions for placement."New value: +"The node to insert (addNode) — same shape as a `nodes` entry: {kind, name, type|op|generatorKey, params, transform}. For kind=generator, generatorKey is one of: gearTrain · planetary · rackPinion · wormDrive · bevelPair · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock. See owlcad://schema/primitives for parameter ranges and owlcad://schema/conventions for placement."
  2. Changed7 schema fields changed
    • addedInput schema / properties / ops / items / properties / customizer
      Added value: +{
+  "description": "Makes the variable a control on the public Customize page (addVariable · setVariable): {public, label, control, min, max, step, unit, group, choices}. control must suit the kind — number: slider|number|toggle|dropdown (dropdown needs choices: [{value, label?}], numeric values); text: text; color: color. A variable drives nothing until a bind op points a node at it.",
+  "type": "object"
+}
    • changedInput schema / properties / ops / items / properties / expr / description
      Previous value: -"The variable’s expression (addVariable · setVariable) — may reference other variables. addVariable creates one; setVariable changes an existing one."New value: +"The variable’s expression (addVariable · setVariable) — may reference other variables. addVariable creates one; setVariable changes an existing one. For bind: the formula (or text/color variable name) that drives `key`; \"\" unbinds."
    • changedInput schema / properties / ops / items / properties / id / description
      Previous value: -"Target node id (updateParams · updateTransform · updateProps · removeNode · reorderNode · reparentNode · wrapModifier · setScriptSource)."New value: +"Target node id (updateParams · updateTransform · updateProps · removeNode · reorderNode · reparentNode · wrapModifier · setScriptSource · bind)."
    • addedInput schema / properties / ops / items / properties / key
      Added value: +{
+  "description": "What to drive (bind): a param key, position.x|y|z, rotation.x|y|z (radians), scale.x|y|z, \"color\", or \"present\".",
+  "type": "string"
+}
    • addedInput schema / properties / ops / items / properties / kind
      Added value: +{
+  "description": "Variable type (addVariable); number is the default.",
+  "enum": [
+    "number",
+    "text",
+    "color"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / ops / items / properties / node / description
      Previous value: -"The node to insert (addNode) — same shape as a `nodes` entry: {kind, name, type|op|generatorKey, params, transform}. For kind=generator, generatorKey is one of: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap. See owlcad://schema/primitives for parameter ranges and owlcad://schema/conventions for placement."New value: +"The node to insert (addNode) — same shape as a `nodes` entry: {kind, name, type|op|generatorKey, params, transform}. For kind=generator, generatorKey is one of: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock. See owlcad://schema/primitives for parameter ranges and owlcad://schema/conventions for placement."
    • changedInput schema / properties / ops / items / properties / op / enum
      Previous value: -[
-  "updateParams",
-  "updateTransform",
-  "updateProps",
-  "addNode",
-  "removeNode",
-  "reorderNode",
-  "reparentNode",
-  "group",
-  "wrapModifier",
-  "addVariable",
-  "setVariable",
-  "setActiveConfig",
-  "ungroup",
-  "unwrapModifier",
-  "bakeGenerator",
-  "makeComponent",
-  "addInstance",
-  "removeComponent",
-  "addPart",
-  "addScript",
-  "setScriptSource",
-  "duplicate",
-  "setScadFile",
-  "removeScadFile"
-]New value: +[
+  "updateParams",
+  "updateTransform",
+  "updateProps",
+  "addNode",
+  "removeNode",
+  "reorderNode",
+  "reparentNode",
+  "group",
+  "wrapModifier",
+  "addVariable",
+  "setVariable",
+  "bind",
+  "setActiveConfig",
+  "ungroup",
+  "unwrapModifier",
+  "bakeGenerator",
+  "makeComponent",
+  "addInstance",
+  "removeComponent",
+  "addPart",
+  "addScript",
+  "setScriptSource",
+  "duplicate",
+  "setScadFile",
+  "removeScadFile"
+]
  3. Changed3 schema fields changed
    • changedInput schema / properties / ops / items / properties / op / enum
      Previous value: -[
-  "updateParams",
-  "updateTransform",
-  "updateProps",
-  "addNode",
-  "removeNode",
-  "reorderNode",
-  "reparentNode",
-  "group",
-  "wrapModifier",
-  "addVariable",
-  "setVariable",
-  "setActiveConfig",
-  "ungroup",
-  "unwrapModifier",
-  "bakeGenerator",
-  "makeComponent",
-  "addInstance",
-  "removeComponent",
-  "addPart",
-  "addScript",
-  "setScriptSource",
-  "duplicate"
-]New value: +[
+  "updateParams",
+  "updateTransform",
+  "updateProps",
+  "addNode",
+  "removeNode",
+  "reorderNode",
+  "reparentNode",
+  "group",
+  "wrapModifier",
+  "addVariable",
+  "setVariable",
+  "setActiveConfig",
+  "ungroup",
+  "unwrapModifier",
+  "bakeGenerator",
+  "makeComponent",
+  "addInstance",
+  "removeComponent",
+  "addPart",
+  "addScript",
+  "setScriptSource",
+  "duplicate",
+  "setScadFile",
+  "removeScadFile"
+]
    • addedInput schema / properties / ops / items / properties / path
      Added value: +{
+  "description": "Project file path scripts include, e.g. lib/dims.scad (setScadFile · removeScadFile).",
+  "type": "string"
+}
    • changedInput schema / properties / ops / items / properties / source / description
      Previous value: -"OpenSCAD script text (addScript · setScriptSource); its Customizer comments become the node’s params."New value: +"OpenSCAD text (addScript · setScriptSource · setScadFile); a script’s Customizer comments become its params."
  4. Changed6 schema fields changed
    • changedInput schema / properties / ops / items / properties / id / description
      Previous value: -"Target node id (updateParams · updateTransform · updateProps · removeNode · reorderNode · reparentNode · wrapModifier)."New value: +"Target node id (updateParams · updateTransform · updateProps · removeNode · reorderNode · reparentNode · wrapModifier · setScriptSource)."
    • changedInput schema / properties / ops / items / properties / ids / description
      Previous value: -"Node ids — two or more to combine (group), one or more to turn into a component (makeComponent). For group with booleanOp=\"difference\" the ORDER is significant: the first id is the body that is kept and every later id is subtracted from it. List the blank first, then the cutters — reversed, you subtract the body from the cutter and usually get an empty result."New value: +"Node ids — two or more to combine (group), one or more to turn into a component (makeComponent) or copy (duplicate). For group with booleanOp=\"difference\" the ORDER is significant: the first id is the body that is kept and every later id is subtracted from it. List the blank first, then the cutters — reversed, you subtract the body from the cutter and usually get an empty result."
    • changedInput schema / properties / ops / items / properties / name / description
      Previous value: -"Node name (updateProps) · variable name (addVariable · setVariable) · component name (makeComponent · addInstance)."New value: +"Node name (updateProps · addScript) · variable name (addVariable · setVariable) · component name (makeComponent · addInstance)."
    • changedInput schema / properties / ops / items / properties / op / enum
      Previous value: -[
-  "updateParams",
-  "updateTransform",
-  "updateProps",
-  "addNode",
-  "removeNode",
-  "reorderNode",
-  "reparentNode",
-  "group",
-  "wrapModifier",
-  "addVariable",
-  "setVariable",
-  "setActiveConfig",
-  "ungroup",
-  "unwrapModifier",
-  "bakeGenerator",
-  "makeComponent",
-  "addInstance",
-  "removeComponent",
-  "addPart"
-]New value: +[
+  "updateParams",
+  "updateTransform",
+  "updateProps",
+  "addNode",
+  "removeNode",
+  "reorderNode",
+  "reparentNode",
+  "group",
+  "wrapModifier",
+  "addVariable",
+  "setVariable",
+  "setActiveConfig",
+  "ungroup",
+  "unwrapModifier",
+  "bakeGenerator",
+  "makeComponent",
+  "addInstance",
+  "removeComponent",
+  "addPart",
+  "addScript",
+  "setScriptSource",
+  "duplicate"
+]
    • changedInput schema / properties / ops / items / properties / ref / description
      Previous value: -"Label for the node this op creates, so a LATER op in the same call can name it as \"@label\" wherever a node id goes (addNode · group) — the only way to subtract a cutter you just added from a body that is not already a difference, and on `group` the only way to build in TWO STAGES: group A and B with a ref, then name that ref to subtract C from the result. Without it the operands of a group stop being top-level and cannot be named again. The label lives for this call only and never reaches the document, which keeps caller-chosen ids out of it. Must be unique within the call and declared before it is used; otherwise the op naming it is refused."New value: +"Label for the node this op creates, so a LATER op in the same call can name it as \"@label\" wherever a node id goes (addNode · group · addScript · duplicate) — the only way to subtract a cutter you just added from a body that is not already a difference, and on `group` the only way to build in TWO STAGES: group A and B with a ref, then name that ref to subtract C from the result. Without it the operands of a group stop being top-level and cannot be named again. The label lives for this call only and never reaches the document, which keeps caller-chosen ids out of it. Must be unique within the call and declared before it is used; otherwise the op naming it is refused."
    • addedInput schema / properties / ops / items / properties / source
      Added value: +{
+  "description": "OpenSCAD script text (addScript · setScriptSource); its Customizer comments become the node’s params.",
+  "type": "string"
+}
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral details beyond annotations: it states the call is transactional ('Every op must apply or the whole call is refused and nothing is written'), describes restructuring capabilities (dissolve a boolean, unwrap a modifier, turn a selection into a component), and mentions a node cap. These are crucial traits for a mutation tool with destructiveHint=true.

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?

The description is front-loaded with the core purpose and key differentiators, then covers transactional behavior, restructuring capabilities, and schema references. Every sentence carries unique value and there is no redundancy.

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

Completeness5/5

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

Given the tool's complexity (24 different ops within an array parameter, nested objects, and destructive nature), the description is complete enough: it orients the agent to the scope, points to the detailed schema resource, and explains the transactional model and restructuring powers. No output schema is needed.

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 coverage is 100% and the schema itself contains rich descriptions for every field. The description adds some high-level meaning (e.g., 'owlcad://schema/edit-ops lists what every op requires; the schema below is a flat bag of every field any op takes') but does not provide per-parameter detail beyond what the schema already offers. Baseline 3 is appropriate when the schema is comprehensive.

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?

The description uses a specific verb+resource ('Make a TARGETED change to one of your projects') and enumerates the kinds of changes (change a parameter, move a node, add or remove one, group nodes, create or set a variable, switch configuration). It also explicitly distinguishes this tool from sibling update_project, making it easy to tell apart.

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?

It gives explicit when-to-use guidance ('Prefer this over update_project when you are changing an existing model') and a prerequisite ('Read with get_project `authored: true` first'). It also alerts the agent to important alternatives and preconditions, leaving little to inference.

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

All OwlCAD toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources