kernelcad

Solve Sketch

solve_sketch

Read-only

Use this when you need to solve a 2D sketch constraint set. Solve a 2D sketch constraint set. Side-effect-free: pass { entities, constraints } and receive solved entities plus the original constraints. Entities are POINT, LINE, and CIRCLE records; constraints use the kernelCAD constraint vocabulary.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`entities`	Yes	Sketch entities to solve. Lines reference point ids; circles reference a center point id.
`constraints`	Yes	Constraints to apply to the entities.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`errors`	No	Solver errors (present on failure).
`entities`	Yes	Solved sketch entities.
`constraints`	Yes	The constraints applied.

Schema Changelog

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

Changed4 schema fields changedJun 19, 2026

addedInput schema / properties / constraints / items / 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 / constraints / items / required
```
Added value: +[
+  "id",
+  "type",
+  "entities"
+]
```

addedInput schema / properties / entities / items / oneOf

Added value: +[
+  {
+    "description": "POINT — a 2D point.",
+    "properties": {
+      "fixed": {
+        "description": "If true, the solver won't move this point.",
+        "type": "boolean"
+      },
+      "id": {
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "POINT"
+        ],
+        "type": "string"
+      },
+      "x": {
+        "type": "number"
+      },
+      "y": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "x",
+      "y"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "LINE — references two point ids.",
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "p1": {
+        "type": "string"
+      },
+      "p2": {
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "LINE"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "p1",
+      "p2"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "CIRCLE — references a center point id.",
+    "properties": {
+      "center": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "radius": {
+        "type": "number"
+      },
+      "type": {
+        "enum": [
+          "CIRCLE"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "center",
+      "radius"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties / entities / items / type
```
Removed value: -"object"
```

Changed4 schema fields changedJun 19, 2026

removedInput schema / properties / constraints / items / 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 / constraints / items / required
```
Removed value: -[
-  "id",
-  "type",
-  "entities"
-]
```

removedInput schema / properties / entities / items / oneOf

Removed value: -[
-  {
-    "description": "POINT — a 2D point.",
-    "properties": {
-      "fixed": {
-        "description": "If true, the solver won't move this point.",
-        "type": "boolean"
-      },
-      "id": {
-        "type": "string"
-      },
-      "type": {
-        "enum": [
-          "POINT"
-        ],
-        "type": "string"
-      },
-      "x": {
-        "type": "number"
-      },
-      "y": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "id",
-      "type",
-      "x",
-      "y"
-    ],
-    "type": "object"
-  },
-  {
-    "description": "LINE — references two point ids.",
-    "properties": {
-      "id": {
-        "type": "string"
-      },
-      "p1": {
-        "type": "string"
-      },
-      "p2": {
-        "type": "string"
-      },
-      "type": {
-        "enum": [
-          "LINE"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "type",
-      "p1",
-      "p2"
-    ],
-    "type": "object"
-  },
-  {
-    "description": "CIRCLE — references a center point id.",
-    "properties": {
-      "center": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "radius": {
-        "type": "number"
-      },
-      "type": {
-        "enum": [
-          "CIRCLE"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "type",
-      "center",
-      "radius"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / entities / items / type
```
Added value: +"object"
```

Changed4 schema fields changedJun 15, 2026

addedInput schema / properties / constraints / items / 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 / constraints / items / required
```
Added value: +[
+  "id",
+  "type",
+  "entities"
+]
```

addedInput schema / properties / entities / items / oneOf

Added value: +[
+  {
+    "description": "POINT — a 2D point.",
+    "properties": {
+      "fixed": {
+        "description": "If true, the solver won't move this point.",
+        "type": "boolean"
+      },
+      "id": {
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "POINT"
+        ],
+        "type": "string"
+      },
+      "x": {
+        "type": "number"
+      },
+      "y": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "x",
+      "y"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "LINE — references two point ids.",
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "p1": {
+        "type": "string"
+      },
+      "p2": {
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "LINE"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "p1",
+      "p2"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "CIRCLE — references a center point id.",
+    "properties": {
+      "center": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "radius": {
+        "type": "number"
+      },
+      "type": {
+        "enum": [
+          "CIRCLE"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "center",
+      "radius"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties / entities / items / type
```
Removed value: -"object"
```

Changed1 schema field changedJun 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "constraints": {
+      "description": "The constraints applied.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "entities": {
+      "description": "Solved sketch entities.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "errors": {
+      "description": "Solver errors (present on failure).",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "entities",
+    "constraints"
+  ],
+  "type": "object"
+}

First observedMay 25, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it is side-effect-free and describes input/output format, but no further behavioral details (e.g., failure modes, constraint validation).

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 efficient sentences: the first gives usage guidance, the second explains side-effect-free and data structures. No redundancy or filler.

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?

The tool has annotations and output schema (not shown but described). The description covers inputs, outputs, behavior, and entity types. Adequate for an agent to select and invoke correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema provides full parameter semantics. The description adds context about entity types and constraint vocabulary, but this is already evident from the schema descriptions.

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 tool solves a 2D sketch constraint set. It uses the verb 'solve' and specifies '2D sketch', distinguishing it from sibling tools like solve_mates (which likely handles 3D assemblies).

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 begins with 'Use this when you need to solve a 2D sketch constraint set', providing clear context. It does not explicitly mention when not to use or alternatives, but the 2D specification implies exclusivity.

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.

Solve Sketch

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources