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

TableJSON 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. 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"
+]
  2. 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."
  3. 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"
+}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already mark destructiveHint=true, and the description adds meaningful behavioral detail beyond that: the call is atomic ('Every op must apply or the whole call is refused and nothing is written'), edits are targeted and do not strand mates, and the tool can restructure the tree. It does not address auth requirements or rate limits, but the atomicity and side-effect framing go beyond the annotations.

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 a single dense paragraph that front-loads the purpose and the most important usage guidance (prefer over update_project, prerequisite, atomicity) before secondary restructure capabilities and the external reference. Every sentence carries operational meaning with no filler or repetition.

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?

The tool is very complex (25 op types, no output schema), but the description compensates with key call semantics: ordered ops, atomicity, authored-id prerequisite, and a pointer to the external edit-ops schema for per-op requirements. It does not describe the success/return payload or error variants, and does not clarify the relationship with edit_nodes, so it is strong but not fully complete.

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%, so the baseline is 3. The top-level description only adds a pointer to owlcad://schema/edit-ops and the caveat that the schema is a flat bag of every field any op takes. It does not explain individual parameter meanings beyond what the schema already provides, which is acceptable but not additive.

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?

The description opens with a specific verb+resource ('Make a TARGETED change to one of your projects') and lists concrete operations like changing a parameter, moving a node, grouping nodes, and setting variables. It explicitly contrasts itself with update_project, but does not distinguish itself from the similarly named sibling edit_nodes, which by name and the node-focused operation list appears to overlap. This is clear but not fully differentiated across all relevant siblings.

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?

It explicitly says when to prefer this tool over update_project ('when you are changing an existing model', because it needs only touched ids and avoids stranding mates) and gives a required prerequisite ('Read with get_project `authored: true` first'). It does not, however, say when edit_nodes would be the better alternative, so the guidance is strong but incomplete.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources