Skip to main content
Glama

CutOptim Engine

Validate a nesting request

validate_nest
Read-onlyIdempotent

Free, no key needed: checks a nesting request without solving it. Same arguments as optimize_nest (field descriptions there). Validate a nest request — free, no key, no quota, no solve. Schema-validate the SAME body /v1/optimize/nest takes, WITHOUT solving or spending a call. Reports engineEnabled (whether the nesting engine is built into this deployment) and warns about parts whose bounding box fits no stock sheet. For engine: "max" the verdict matches the optimize path exactly: 400 for anything outside the preview scope, 503 where the async tier is not enabled, and otherwise a warning that the job will be asynchronous. See /v1/validate/2d.

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": {
      "parts": "<parts>",
      "stock": "<stock>"
    },
    "name": "validate_nest"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsYesOne or more parts to nest, one NestPart per row.
stockYesOne or more sheet types, one NestStock per row.
engineNo`lbf` (default) is single-pass, synchronous and instant. `max` is ASYNCHRONOUS: 202 + poll `GET /v1/jobs/{id}`; it runs `lbf` first, then a time-budgeted search that fills sheets one at a time looking for FEWER sheets, and never returns more than `lbf`, nor a plan that ranks worse (price with `minimizeCost`, otherwise sheet area). It accepts several sheet sizes per material and `respectStock`; a `polygon` sheet or exclusion zones are served by `lbf` inside the job, with a warning. `sparrow` is a deprecated alias of `max`.lbf
includeNoAdditive inline export of the achieved layout. `svg` returns a self-contained, styled `<svg>` string (one titled band per sheet, parts drawn as filled polygons with holes, exclusion zones hatched); `dxf` returns an R12 document (closed `POLYLINE`/`VERTEX` outlines on STOCK/PARTS/HOLES/ZONES layers, part names on LABELS). Both are unit-agnostic, exactly like the request coordinates. The geometry in `sheets[]` is returned either way.
optionsNoSolve options. All optional.

Output Schema

NameRequiredDescriptionDefault
modeYes
partsYes
stockYes
validYes
warningsYes
engineEnabledNo
contractVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / stock / items / properties / maxLength
      Added value: +{
      +  "exclusiveMinimum": 0,
      +  "maximum": 200000,
      +  "type": "number"
      +}
    • addedInput schema / properties / stock / items / properties / roll
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed5 schema fields changed
    • addedInput schema / properties / engine / description
      Added value: +"`lbf` (default) is single-pass, synchronous and instant. `max` is ASYNCHRONOUS: 202 + poll `GET /v1/jobs/{id}`; it runs `lbf` first, then a time-budgeted search that fills sheets one at a time looking for FEWER sheets, and never returns more than `lbf`, nor a plan that ranks worse (price with `minimizeCost`, otherwise sheet area). It accepts several sheet sizes per material and `respectStock`; a `polygon` sheet or exclusion zones are served by `lbf` inside the job, with a warning. `sparrow` is a deprecated alias of `max`."
    • addedInput schema / properties / include / description
      Added value: +"Additive inline export of the achieved layout. `svg` returns a self-contained, styled `<svg>` string (one titled band per sheet, parts drawn as filled polygons with holes, exclusion zones hatched); `dxf` returns an R12 document (closed `POLYLINE`/`VERTEX` outlines on STOCK/PARTS/HOLES/ZONES layers, part names on LABELS). Both are unit-agnostic, exactly like the request coordinates. The geometry in `sheets[]` is returned either way."
    • addedInput schema / properties / options / description
      Added value: +"Solve options. All optional."
    • addedInput schema / properties / parts / description
      Added value: +"One or more parts to nest, one NestPart per row."
    • addedInput schema / properties / stock / description
      Added value: +"One or more sheet types, one NestStock per row."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the readOnly/idempotent annotations: no key, no quota, no solve call consumed, reports `engineEnabled`, warns about parts whose bounding box fits no stock sheet, and pins down `engine: "max"` verdicts to concrete 400/503/asynchronous-warning outcomes. This is exactly the kind of pre-call outcome disclosure that lets an agent predict results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical framing is front-loaded, but 'free, no key' appears three times and 'without solving' is restated as 'WITHOUT solving or spending a call' plus 'no solve'. Trimming that repetition would make the useful content (engine:max verdicts, engineEnabled, bounding-box warnings) stand out more.

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 validator whose output schema already defines the return shape, the description covers everything else the agent needs: cost/access model, what is and isn't executed, the special `engine: "max"` verdicts, and where field docs live. Nothing material is missing.

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 description coverage is 100%, so the schema already carries most parameter meaning; the description goes beyond it by specifying the response semantics of the `engine` parameter (max → 400/503/async warning) and by noting arguments mirror `optimize_nest`. It does not add new detail for `parts`/`stock`, which the schema covers well.

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 and resource ('schema-validate the SAME body `/v1/optimize/nest` takes') and explicitly contrasts with the sibling that does the real work ('WITHOUT solving or spending a call'), naming `optimize_nest` directly. An agent can immediately tell this is the dry-run counterpart to the solve tool.

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?

Gives a clear condition for calling it — validate a request body before spending a solve call — and points to `optimize_nest` for the authoritative field documentation. It lacks an explicit 'do not use this when…' exclusion, but the intent (free pre-flight check) is unambiguous.

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.