Skip to main content
Glama

kernelcad

by com.kernelcad

Verify Design

verify
Read-only

Use this when you need to check a design against a rule set. One verifier, selected by check:

  • 'assembly' — mate-aware assembly validator on the active session (run evaluate_script first).

  • 'urdf' — structural validity of a .urdf file ({ urdf_path }).

  • 'dfm' — print-readiness gates declared by dfmSpec() ({ file | code }).

  • 'dfm-preflight' — sheet-metal flat pattern vs a job-shop's ordering rules ({ vendor, material, thicknessIn|thicknessMm, ... }).

  • 'swept-collision' — sweep declared joint range(s) and report colliding poses.

  • 'reachable' — inverse-kinematics reachability for an end-effector ({ tip_link, target_position, ... }).

  • 'mounting-holes' — fastened mates expose matching hole diameters on both sides.

  • 'load-capacity' — closed-form Euler-Bernoulli beam stress / safety-factor check ({ loads, materials, ... }). All params except check are check-specific and forwarded verbatim; each check fails closed on its own missing required params.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dxfNocheck:'dfm-preflight' — path to a DXF file.
codeNoInline kernelCAD script source (same checks as `file`).
fileNoPath to a .kcad.ts script (assembly/dfm/dfm-preflight/swept-collision/reachable/mounting-holes/load-capacity).
modeNocheck:'load-capacity' — 'beam' (default) or 'stub'.
seedNocheck:'reachable' — numeric IK seed pose (joint name -> deg/mm).
checkYesWhich verification to run.
jointNocheck:'swept-collision' — joint to sweep; omit to sweep every declared joint.
loadsNocheck:'load-capacity' — partName -> { force?: [Fx,Fy,Fz] N, torque?: [Tx,Ty,Tz] N*m }.
rangeNocheck:'swept-collision' — [lower, upper, step] in joint-native units.
vendorNocheck:'dfm-preflight' — vendor SKU (required for that check).
serviceNocheck:'dfm-preflight' — service.
assemblyNoAssembly name; defaults to the first captured assembly.
materialNocheck:'dfm-preflight' — material SKU (required for that check).
tip_linkNocheck:'reachable' — end-effector part name (required for that check).
featureIdNocheck:'dfm-preflight' — FeatureId to scope to.
materialsNocheck:'load-capacity' — partName -> material declaration.
urdf_pathNocheck:'urdf' — path to the .urdf file.
thicknessInNocheck:'dfm-preflight' — material thickness in inches.
thicknessMmNocheck:'dfm-preflight' — material thickness in millimeters.
prefer_solverNocheck:'reachable' — force the IK path ('auto' default).
max_iterationsNocheck:'reachable' — numeric-path iteration cap.
refreshCatalogNocheck:'dfm-preflight' — force vendor catalog refresh.
target_positionNocheck:'reachable' — target [x, y, z] mm (world frame).
target_orientationNocheck:'reachable' — target XYZ Euler angles in radians.
position_tolerance_mmNocheck:'reachable' — position tolerance in mm.
collision_tolerance_mm3Nocheck:'swept-collision' — BREP intersection volume tolerance (mm^3).
safety_factor_thresholdNocheck:'load-capacity' — pass/fail safety-factor floor (default 1.5).
orientation_tolerance_radNocheck:'reachable' — orientation tolerance in radians.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the verification ran and passed its gate.
errorNoFailure message (present on failure).
errorCodeNo
diagnosticsNoVerifier diagnostics (most checks).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. Description adds that each check 'fails closed on missing required params' and implies safe, non-destructive behavior. Does not detail output, but output schema covers that.

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?

Concise and well-structured: one sentence intro, then bulleted list of checks. Each bullet is brief. No redundant or irrelevant information. Front-loaded with purpose.

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?

Given 28 parameters, 100% schema coverage, output schema, and annotations, the description is highly complete. It covers all check types, parameter grouping, usage rules, and prerequisites. Only minor gap is explicit output explanation, but covered by output schema.

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 has 100% coverage with individual parameter descriptions. Description adds value by grouping parameters per check (e.g., { urdf_path }) and explaining that all params except `check` are check-specific. This structuring compensates for flat schema.

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?

Description clearly states purpose: 'check a design against a rule set' and lists 8 specific check types with brief explanations. Distinguishes from siblings like evaluate_script by focusing on rule verification.

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?

Opens with 'Use this when...' and provides check-specific context (e.g., 'run evaluate_script first' for assembly). States parameter forwarding and failure behavior. Lacks explicit alternatives or when-not-to-use, but overall clear.

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

All kernelcad toolsInspect
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.

Resources