Skip to main content
Glama

Cut a model that does not fit the bed

split_for_printing
Destructive

Cut one body in a project into two halves at a plane, replacing it, with a joint so they go back together after printing; the reply lists the new bodies. This is the answer to "my model is too big for my printer". Both halves stay fully parametric — each is the original body intersected with a half-space, not a flattened mesh — so they still export as solids and still open for editing. Pick the joint by what the print needs: dowel puts a socket in BOTH halves and prints the pin separately, so neither half has anything standing off its cut face and a wrong fit costs a two-gram reprint instead of a whole half; pin and tenon grow the key out of one half; bolt is the only one that comes apart again. Omit position to cut through the middle of the body on that axis.

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": {
      "projectId": "<projectId>",
      "nodeId": "<nodeId>"
    },
    "name": "split_for_printing"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNoHow much slack the key gets in its socket. Defaults to normal (0.4 mm total). Use `custom` with `gap` to set it yourself.
gapNoTOTAL clearance across the key in mm when `fit` is custom, as a fit coupon reads it (each side gets half). Default 0.4.
axisNoWhich way the plane faces. Cut a tall part across z, a long one across x. Defaults to z.
sizeNoKey size in mm — pin/dowel diameter, tenon width, bolt size. Defaults to 5.
countNoHow many keys across the cut face (1-6). Defaults to 2.
depthNoHow far a key reaches into the far half, mm. For a dowel, into EACH half. Defaults to 6.
jointNoDefaults to pin.
shapeNoKey cross-section (pin and dowel only). Round lets the halves spin about a single key; any other shape stops that. Defaults to circle.
styleNoStraight or tapered (pin and dowel only). Tapered is easier to start and shrinks the flat bridge over a blind socket. Defaults to prism.
nodeIdYesThe top-level body to cut, from `get_project`. A nested node, a generator or a component instance cannot be cut — the cut is authored in world coordinates.
versionNoThe `version` get_project reported, so a concurrent change is detected rather than overwritten.
positionNoWhere the plane sits along `axis`, in world mm. Must pass THROUGH the body — the reply names the legal range if it does not. Omit to cut at the middle, which is almost always what you want.
projectIdYesThe project containing the body to cut.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / fit / description
      Previous value: -"How much slack the key gets in its socket. Defaults to normal (0.2 mm). Use `custom` with `gap` to set it yourself."New value: +"How much slack the key gets in its socket. Defaults to normal (0.4 mm total). Use `custom` with `gap` to set it yourself."
    • changedInput schema / properties / gap / description
      Previous value: -"The clearance in mm when `fit` is custom."New value: +"TOTAL clearance across the key in mm when `fit` is custom, as a fit coupon reads it (each side gets half). Default 0.4."
  2. Changed1 schema field changed
    • addedInput schema / properties / projectId / description
      Added value: +"The project containing the body to cut."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive=true and readOnly=false, but the description goes further: it says the original body is replaced, that both halves stay fully parametric as half-space intersections rather than flattened meshes, and that they still export as solids and remain editable. That is exactly the consequence information an agent needs before invoking a destructive modeling operation.

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?

Every sentence carries load and the core action is front-loaded in the first clause. It is one dense paragraph, though; the joint options would scan faster as a short list rather than semicolon-chained prose.

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?

For a 13-parameter destructive mutation with no output schema, the description covers what is replaced, what the reply contains, how the geometry survives, how to choose the risky parameter, and how defaults behave. Nothing material is missing for correct invocation.

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 100%, so the baseline is 3, and the description earns above that by explaining joint semantics the schema leaves at "Defaults to pin" — socket in both halves for `dowel`, key grown from one half for `pin`/`tenon`, re-openable only for `bolt` — plus the constraint that `position` must pass through the body and the default of cutting at the middle.

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?

Opens with a specific verb and resource plus the full transformation: "Cut one body in a project into two halves at a plane, replacing it, with a joint so they go back together after printing." It also states the reply shape ("the reply lists the new bodies") and frames the user intent, leaving no ambiguity against siblings like export or repair_project.

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 triggering situation ("This is the answer to 'my model is too big for my printer'") and gives a decision rule for the hardest parameter: which joint to pick based on print needs, including that `bolt` is the only re-openable option and `dowel` moves the risk into a cheap separate pin. It also tells when to omit `position`.

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