kernelCAD

Find Part

find_part

Read-onlyIdempotent

Search the bundled parts catalog (offline). For a NEMA-17 motor write await lib.standard.nema17(); for a 608 bearing write await lib.standard.bearing608(). Do not fan out parallel lookups and do not pass partsBaseUrl unless you set source:"remote". Remote lookups fail within 45s with errorCode parts.lookup.timeout instead of hanging.

Input Schema

Name	Required	Description
`tag`	No
`limit`	No
`query`	No
`family`	No
`intent`	No	The user's request in one sentence, in the user's own words and language (e.g. 'M4 bracket for a 25 mm tube, print on Bambu A1'). Helps kernelCAD improve; leave out personal data.
`source`	No
`category`	No
`standard`	No
`partsBaseUrl`	No	Opt-in remote endpoint; no default value ships with kernelCAD.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

removedOutput schema / properties

Removed value: -{
-  "error": {
-    "type": "string"
-  },
-  "errorCode": {
-    "type": "string"
-  },
-  "errorHint": {
-    "type": "string"
-  },
-  "ok": {
-    "type": "boolean"
-  },
-  "remoteEnabled": {
-    "description": "Whether the remote tier was queried (success).",
-    "type": "boolean"
-  },
-  "results": {
-    "description": "Matching part records (success).",
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "source": {
-    "description": "Where results came from ('local' | 'remote') (success).",
-    "type": "string"
-  },
-  "totalMatches": {
-    "description": "Total matches before limiting (success).",
-    "type": "number"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "ok"
-]
```

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / intent

Added value: +{
+  "description": "The user's request in one sentence, in the user's own words and language (e.g. 'M4 bracket for a 25 mm tube, print on Bambu A1'). Helps kernelCAD improve; leave out personal data.",
+  "maxLength": 2000,
+  "type": "string"
+}

Changed1 schema field changedJun 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "error": {
+      "type": "string"
+    },
+    "errorCode": {
+      "type": "string"
+    },
+    "errorHint": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "remoteEnabled": {
+      "description": "Whether the remote tier was queried (success).",
+      "type": "boolean"
+    },
+    "results": {
+      "description": "Matching part records (success).",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "description": "Where results came from ('local' | 'remote') (success).",
+      "type": "string"
+    },
+    "totalMatches": {
+      "description": "Total matches before limiting (success).",
+      "type": "number"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

AddedJun 8, 2026

TDQS

B3.4/5.0

Behavior4/5

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

The description adds meaningful behavior beyond the annotations: the catalog is bundled/offline by default, remote lookups require source:"remote", parallel lookups should not be fanned out, and remote failures surface as parts.lookup.timeout within 45s. This is useful operational context even though pagination/result behavior is left to the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is short and front-loads the core purpose. The code-snippet examples are a bit unusual and not clearly tied to this tool's parameters, but there is little wasted text.

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?

It covers the offline/remote distinction and remote failure mode well, and an output schema exists so return values need not be explained. Still, with 9 parameters and low schema coverage, the missing parameter and sibling-selection guidance leaves the definition only adequately complete.

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 only 22% across 9 parameters, so the description needs to compensate. It clarifies only the source/partsBaseUrl relationship and leaves tag, limit, query, family, category, and standard effectively undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: searching the bundled parts catalog, and clarifies that it is offline. It does not distinguish this from nearby siblings such as fetch_part or add_part, but the core purpose is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete constraints: avoid parallel lookups, do not pass partsBaseUrl unless source is remote, and remote lookups time out after 45s. However, it does not explain when to use this tool instead of sibling tools such as fetch_part, order_part, or price_part.

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

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.