CutOptim Engine

Validate a 1D request

validate_1d

Read-onlyIdempotent

Free, no key needed: checks a 1D request without solving it. Same arguments as optimize_1d (field descriptions there). Validate a 1D request — free, no key, no quota, no solve. Schema-validate the SAME body /v1/optimize/1d takes, WITHOUT solving or spending a call. See /v1/validate/2d.

Input Schema

Name	Required	Default
`parts`	Yes
`stock`	Yes
`engine`	No	heuristic
`include`	No
`options`	No

Output Schema

Name	Required	Description	Default
`mode`	Yes
`parts`	Yes
`stock`	Yes
`valid`	Yes
`warnings`	Yes
`engineEnabled`	No
`contractVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 24, 2026

addedInput schema / properties / options / properties / mitrePairing
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```

addedInput schema / properties / parts / items / properties / depth

Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / parts / items / properties / ends

Added value: +{
+  "properties": {
+    "end": {
+      "properties": {
+        "angle": {
+          "exclusiveMaximum": 90,
+          "exclusiveMinimum": -90,
+          "type": "number"
+        },
+        "bevel": {
+          "default": 0,
+          "exclusiveMaximum": 90,
+          "exclusiveMinimum": -90,
+          "type": "number"
+        }
+      },
+      "required": [
+        "angle"
+      ],
+      "type": "object"
+    },
+    "start": {
+      "properties": {
+        "angle": {
+          "exclusiveMaximum": 90,
+          "exclusiveMinimum": -90,
+          "type": "number"
+        },
+        "bevel": {
+          "default": 0,
+          "exclusiveMaximum": 90,
+          "exclusiveMinimum": -90,
+          "type": "number"
+        }
+      },
+      "required": [
+        "angle"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / parts / items / properties / flip

Added value: +{
+  "default": "none",
+  "enum": [
+    "none",
+    "face",
+    "edge",
+    "any"
+  ],
+  "type": "string"
+}

addedInput schema / properties / parts / items / properties / thickness
```
Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
```

First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing cost and auth traits the annotations don't cover: free, no API key required, no quota consumed, and no solve performed. That is exactly the operational context an agent needs before choosing this over optimize_1d. It does not describe what a failed validation looks like or rate limits, keeping it short of 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.

Conciseness2/5

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

The core fact — free, no key, no solve — is restated three separate times ('Free, no key needed', 'free, no key, no quota, no solve', 'WITHOUT solving or spending a call'), so the text is roughly double the needed length. It is front-loaded, but several clauses do not earn their place.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the tool's core contract (same body as optimize_1d, no solve) is conveyed. However, for a nested five-parameter payload with zero schema coverage, the agent still lacks any in-definition sense of what makes a body valid or what the error shape is, leaving it dependent on cross-referencing optimize_1d.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% on a five-parameter schema with nested objects and an enum, and the description compensates only by delegating: 'Same arguments as optimize_1d (field descriptions there).' That pointer is better than nothing but forces a second tool lookup and leaves required vs optional, nesting, and the engine/include enums unexplained in either place.

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 ('checks/validates a 1D request') and immediately distinguishes it from the sibling it could be confused with: same body as optimize_1d but 'WITHOUT solving or spending a call'. An agent can tell it apart from optimize_1d without opening either 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?

Explicitly positions itself as the pre-flight alternative to optimize_1d by noting it takes 'the SAME body /v1/optimize/1d takes, WITHOUT solving or spending a call', which tells the agent when to prefer it. It names the alternative but does not spell out when-not-to-use (e.g. after a successful solve, or for 2D payloads beyond a bare URL reference).

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

All CutOptim Engine tools Inspect

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.