CutOptim Engine

Validate a timber request

validate_wood

Read-onlyIdempotent

Free, no key needed: checks a timber request without solving it. Same arguments as optimize_wood (field descriptions there). Validate a wood request — free, no key, no quota, no solve. Schema-validate the SAME body /v1/optimize/wood takes, WITHOUT solving or spending a call. Warnings flag parts with no matching-section stock long enough. 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.

Changed3 schema fields changedOct 24, 2026

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

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"
+}

First observedOct 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations: it is free, requires no key/quota, does not solve, and emits warnings for parts with no matching stock section.

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 purpose is front-loaded and the structure is understandable, but the description repeats 'free, no key, no quota, no solve' multiple times. That redundancy wastes space without adding clarity.

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?

The tool has a nested schema, 0% parameter description coverage, and an output schema. The description covers the key behavioral distinction from optimize_wood, but it does not adequately explain the input body beyond pointing to the sibling tool.

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%, and the description does not explain the five parameters (parts, stock, engine, include, options) or their semantics. Referencing optimize_wood for field descriptions is an external cross-reference, but it does not compensate for the missing parameter guidance here.

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 states a specific verb and resource: validate a timber/wood request without solving it. It explicitly distinguishes this from optimize_wood by saying it does NOT solve or spend a call, so an agent can tell the two apart before 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?

It clearly positions the tool as a free pre-check before calling optimize_wood, with the condition that it avoids solving or spending a call. It does not explicitly state when not to use it or how to choose among validate_1d/2d/nest, but the sibling comparison is adequate.

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.