kernelcad

Add Constraint

add_constraint

Use this when you need to add a sketch constraint to a list. Append one validated sketch constraint to a constraint list. Side-effect-free: pass { constraints, constraint } and receive the updated list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`constraint`	Yes	The constraint to append.
`constraints`	No	Existing constraint list to append to (omit for an empty list).

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`errors`	No	Validation errors (present on failure).
`constraints`	Yes	Updated constraint list.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed6 schema fields changedJun 19, 2026

addedInput schema / properties / constraint / description
```
Added value: +"The constraint to append."
```

addedInput schema / properties / constraint / properties

Added value: +{
+  "entities": {
+    "description": "Ids of the entities the constraint relates.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "id": {
+    "type": "string"
+  },
+  "type": {
+    "enum": [
+      "COINCIDENT",
+      "DISTANCE",
+      "HORIZONTAL",
+      "VERTICAL",
+      "PARALLEL",
+      "PERPENDICULAR",
+      "EQUAL_LENGTH",
+      "TANGENT",
+      "RADIUS",
+      "ANGLE",
+      "CONCENTRIC",
+      "SYMMETRIC"
+    ],
+    "type": "string"
+  },
+  "value": {
+    "description": "Required for DISTANCE, RADIUS, and ANGLE.",
+    "type": "number"
+  }
+}

addedInput schema / properties / constraint / required

Added value: +[
+  "id",
+  "type",
+  "entities"
+]

addedInput schema / properties / constraints / description

Added value: +"Existing constraint list to append to (omit for an empty list)."

addedInput schema / properties / constraints / items / properties

Added value: +{
+  "entities": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "id": {
+    "type": "string"
+  },
+  "type": {
+    "enum": [
+      "COINCIDENT",
+      "DISTANCE",
+      "HORIZONTAL",
+      "VERTICAL",
+      "PARALLEL",
+      "PERPENDICULAR",
+      "EQUAL_LENGTH",
+      "TANGENT",
+      "RADIUS",
+      "ANGLE",
+      "CONCENTRIC",
+      "SYMMETRIC"
+    ],
+    "type": "string"
+  },
+  "value": {
+    "type": "number"
+  }
+}

addedInput schema / properties / constraints / items / required
```
Added value: +[
+  "id",
+  "type",
+  "entities"
+]
```

Changed6 schema fields changedJun 19, 2026

removedInput schema / properties / constraint / description
```
Removed value: -"The constraint to append."
```

removedInput schema / properties / constraint / properties

Removed value: -{
-  "entities": {
-    "description": "Ids of the entities the constraint relates.",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "id": {
-    "type": "string"
-  },
-  "type": {
-    "enum": [
-      "COINCIDENT",
-      "DISTANCE",
-      "HORIZONTAL",
-      "VERTICAL",
-      "PARALLEL",
-      "PERPENDICULAR",
-      "EQUAL_LENGTH",
-      "TANGENT",
-      "RADIUS",
-      "ANGLE",
-      "CONCENTRIC",
-      "SYMMETRIC"
-    ],
-    "type": "string"
-  },
-  "value": {
-    "description": "Required for DISTANCE, RADIUS, and ANGLE.",
-    "type": "number"
-  }
-}

removedInput schema / properties / constraint / required

Removed value: -[
-  "id",
-  "type",
-  "entities"
-]

removedInput schema / properties / constraints / description

Removed value: -"Existing constraint list to append to (omit for an empty list)."

removedInput schema / properties / constraints / items / properties

Removed value: -{
-  "entities": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "id": {
-    "type": "string"
-  },
-  "type": {
-    "enum": [
-      "COINCIDENT",
-      "DISTANCE",
-      "HORIZONTAL",
-      "VERTICAL",
-      "PARALLEL",
-      "PERPENDICULAR",
-      "EQUAL_LENGTH",
-      "TANGENT",
-      "RADIUS",
-      "ANGLE",
-      "CONCENTRIC",
-      "SYMMETRIC"
-    ],
-    "type": "string"
-  },
-  "value": {
-    "type": "number"
-  }
-}

removedInput schema / properties / constraints / items / required
```
Removed value: -[
-  "id",
-  "type",
-  "entities"
-]
```

Changed6 schema fields changedJun 15, 2026

addedInput schema / properties / constraint / description
```
Added value: +"The constraint to append."
```

addedInput schema / properties / constraint / properties

Added value: +{
+  "entities": {
+    "description": "Ids of the entities the constraint relates.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "id": {
+    "type": "string"
+  },
+  "type": {
+    "enum": [
+      "COINCIDENT",
+      "DISTANCE",
+      "HORIZONTAL",
+      "VERTICAL",
+      "PARALLEL",
+      "PERPENDICULAR",
+      "EQUAL_LENGTH",
+      "TANGENT",
+      "RADIUS",
+      "ANGLE",
+      "CONCENTRIC",
+      "SYMMETRIC"
+    ],
+    "type": "string"
+  },
+  "value": {
+    "description": "Required for DISTANCE, RADIUS, and ANGLE.",
+    "type": "number"
+  }
+}

addedInput schema / properties / constraint / required

Added value: +[
+  "id",
+  "type",
+  "entities"
+]

addedInput schema / properties / constraints / description

Added value: +"Existing constraint list to append to (omit for an empty list)."

addedInput schema / properties / constraints / items / properties

Added value: +{
+  "entities": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "id": {
+    "type": "string"
+  },
+  "type": {
+    "enum": [
+      "COINCIDENT",
+      "DISTANCE",
+      "HORIZONTAL",
+      "VERTICAL",
+      "PARALLEL",
+      "PERPENDICULAR",
+      "EQUAL_LENGTH",
+      "TANGENT",
+      "RADIUS",
+      "ANGLE",
+      "CONCENTRIC",
+      "SYMMETRIC"
+    ],
+    "type": "string"
+  },
+  "value": {
+    "type": "number"
+  }
+}

addedInput schema / properties / constraints / items / required
```
Added value: +[
+  "id",
+  "type",
+  "entities"
+]
```

Changed1 schema field changedJun 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "constraints": {
+      "description": "Updated constraint list.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "errors": {
+      "description": "Validation errors (present on failure).",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "constraints"
+  ],
+  "type": "object"
+}

First observedMay 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Description explicitly states 'Side-effect-free' which aligns with destructiveHint=false. It explains the tool returns the updated list, indicating no mutation of inputs. This adds valuable behavioral context beyond 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?

Two sentences, no redundant words. Front-loaded with purpose. Every sentence contributes necessary information.

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?

Given the tool has 2 parameters, nested objects, and output schema, the description covers purpose, usage pattern, and side-effect-free behavior. It does not detail output format, but output schema exists. Minor gap: could mention the output is a new list.

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%. Description adds meaning by explaining the role of each parameter: 'constraints' as existing list (omit for empty), 'constraint' as the one to append. Also mentions 'validated' which hints at input validation.

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 clearly states the verb 'add' and resource 'sketch constraint to a list'. It distinguishes from siblings by specifying the domain (sketch constraint) and the action (appending to a list).

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?

The description gives explicit context: 'Use this when you need to add a sketch constraint to a list.' It also provides usage pattern: 'pass { constraints, constraint } and receive the updated list.' It does not mention when not to use or alternatives, but context is clear.

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

All kernelcad tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Tools are mostly distinct, with clear descriptions for each. However, there is some potential overlap between inspection tools like 'inspect' and 'mesh_summary', and between rendering tools 'render_preview' and 'get_latest_render', which could cause minor confusion.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, making it predictable for an agent to infer functionality.

Tool Count2/5

44 tools is significantly higher than the typical well-scoped range of 3-15. While the domain is complex, the count feels excessive and could overwhelm an agent.

Completeness4/5

The tool set covers an extensive range of CAD operations including creation, inspection, rendering, export, and verification. Minor gaps exist, such as direct sketch editing tools, but overall it is comprehensive.

Add Constraint

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources