kernelCAD

Get Project

get_project

Read-only

Use this when you need to reopen a saved project or browse what the user has saved — it fetches a kernelCAD Studio project, or lists the signed-in user's saved projects. Pass slug (from a /p/ link or a prior listing) to fetch that project's full .kcad source and metadata — then edit and open_in_studio with the same slug so the user's open tab updates live. Private projects require their owner's OAuth connection. OMIT slug to list the signed-in user's saved projects (most recently updated first); that listing mode requires the OAuth connection and does NOT paint — prefer list_my_projects to find a project to continue. Read-only: this tool never shows a viewer (only open_in_studio does, once per response). Paint phases: projectSaved/meshReady reflect fetch state; viewerPainted stays false. Use open_in_studio (with code) to publish+paint — do NOT call get_model_mesh or get_latest_render for interactive paint.

Input Schema

Name	Required	Description	Default
`slug`	No	The project slug from a listing or a /p/<slug> Studio link. Omit to list the signed-in user's saved projects.

Output Schema

Name	Required	Description
`ok`	No	Whether the read succeeded.
`url`	No	Fetch mode: revision-pinned /p/<slug>?version= link.
`code`	No	Fetch mode: the full .kcad source.
`slug`	No	Fetch mode: the project slug.
`title`	No	Fetch mode: the project title.
`assets`	No	Complementary files keyed by source-relative path.
`meshUrl`	No	Fetch mode: revision-matched mesh artifact URL when available — FunnelViewer loads it instead of re-executing CAD. When meshStatus is building, this is the expected CDN URL (retry until ready).
`privacy`	No	Fetch mode: the project privacy.
`version`	No	Fetch mode: the project version.
`embedUrl`	No	Fetch mode: revision-pinned chrome-free /embed/<slug>?revision= viewer URL (includes meshUrl when available).
`meshHint`	No	Fetch mode: when meshStatus=building — transient; poll again or re-open_in_studio; never imply permanent 404.
`projects`	No	List mode (no slug): the user's saved projects.
`meshError`	No	Fetch mode: sanitized repair/persist error when meshStatus is failed.
`meshReady`	No	Fetch mode: true only when meshStatus===ready.
`paintHint`	No
`meshStatus`	No	Fetch mode: ready \| building \| failed \| missing — explicit CDN artifact state (never silently omit meshUrl under CDN mode).
`parameters`	No	Fetch mode: the model's editable parameters.
`updated_at`	No	Fetch mode: last-updated timestamp.
`serverBuild`	No	Deploy identity (package+git SHA@boot time) so connector lag is observable.
`projectSaved`	No	Fetch mode: true when the project was loaded.
`viewerPainted`	No	Always false on tools/call; widget sets true after correlated model_displayed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

addedOutput schema / properties / meshHint

Added value: +{
+  "description": "Fetch mode: when meshStatus=building — transient; poll again or re-open_in_studio; never imply permanent 404.",
+  "type": "string"
+}

Changed4 schema fields changedSep 23, 2026

addedOutput schema / properties / meshReady

Added value: +{
+  "description": "Fetch mode: true only when meshStatus===ready.",
+  "type": "boolean"
+}

addedOutput schema / properties / paintHint
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / projectSaved

Added value: +{
+  "description": "Fetch mode: true when the project was loaded.",
+  "type": "boolean"
+}

addedOutput schema / properties / viewerPainted

Added value: +{
+  "description": "Always false on tools/call; widget sets true after correlated model_displayed.",
+  "type": "boolean"
+}

Changed3 schema fields changedSep 23, 2026

addedOutput schema / properties / meshError

Added value: +{
+  "description": "Fetch mode: sanitized repair/persist error when meshStatus is failed.",
+  "type": "string"
+}

addedOutput schema / properties / meshStatus

Added value: +{
+  "description": "Fetch mode: ready | building | failed | missing — explicit CDN artifact state (never silently omit meshUrl under CDN mode).",
+  "type": "string"
+}

changedOutput schema / properties / meshUrl / description

Previous value: -"Fetch mode: revision-matched mesh artifact URL when available — FunnelViewer loads it instead of re-executing CAD."New value: +"Fetch mode: revision-matched mesh artifact URL when available — FunnelViewer loads it instead of re-executing CAD. When meshStatus is building, this is the expected CDN URL (retry until ready)."

Changed4 schema fields changedSep 22, 2026

addedOutput schema / properties / embedUrl

Added value: +{
+  "description": "Fetch mode: revision-pinned chrome-free /embed/<slug>?revision= viewer URL (includes meshUrl when available).",
+  "type": "string"
+}

addedOutput schema / properties / meshUrl

Added value: +{
+  "description": "Fetch mode: revision-matched mesh artifact URL when available — FunnelViewer loads it instead of re-executing CAD.",
+  "type": "string"
+}

addedOutput schema / properties / serverBuild

Added value: +{
+  "description": "Deploy identity (package+git SHA@boot time) so connector lag is observable.",
+  "type": "string"
+}

addedOutput schema / properties / url

Added value: +{
+  "description": "Fetch mode: revision-pinned /p/<slug>?version= link.",
+  "type": "string"
+}

Changed1 schema field changedJul 27, 2026

addedOutput schema / properties / assets

Added value: +{
+  "additionalProperties": true,
+  "description": "Complementary files keyed by source-relative path.",
+  "type": "object"
+}

Changed1 schema field changedJun 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "code": {
+      "description": "Fetch mode: the full .kcad source.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the read succeeded.",
+      "type": "boolean"
+    },
+    "parameters": {
+      "description": "Fetch mode: the model's editable parameters.",
+      "items": {},
+      "type": "array"
+    },
+    "privacy": {
+      "description": "Fetch mode: the project privacy.",
+      "type": "string"
+    },
+    "projects": {
+      "description": "List mode (no slug): the user's saved projects.",
+      "items": {},
+      "type": "array"
+    },
+    "slug": {
+      "description": "Fetch mode: the project slug.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Fetch mode: the project title.",
+      "type": "string"
+    },
+    "updated_at": {
+      "description": "Fetch mode: last-updated timestamp.",
+      "type": "string"
+    },
+    "version": {
+      "description": "Fetch mode: the project version.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedJun 13, 2026

changedInput schema / properties / slug / description

Previous value: -"The project slug from list_my_projects or a /p/<slug> Studio link."New value: +"The project slug from a listing or a /p/<slug> Studio link. Omit to list the signed-in user's saved projects."

removedInput schema / required
```
Removed value: -[
-  "slug"
-]
```

AddedJun 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnlyHint, destructiveHint=false), but the description goes well beyond them: it discloses that private projects and listing mode require the owner's OAuth connection, that listing mode does not paint, and it explains the paint-phase semantics (projectSaved/meshReady reflect fetch state; viewerPainted stays false). That is unusually rich behavioral context for a read tool.

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?

Purpose and mode selection are front-loaded, but the back half is dense jargon ('Paint phases: projectSaved/meshReady ... viewerPainted stays false') that is hard to parse and would benefit from restructuring. The sentences are information-packed rather than wasteful, but the wall-of-text delivery hurts readability.

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?

With a rich output schema and full annotations, the description needn't explain return values, and it covers both modes, auth requirements, alternatives, and paint behavior. The only gap is that the paint-phase explanation is cryptic rather than clarifying, but functionally an agent has everything needed to call it 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%, and the schema already documents that `slug` comes from a listing or /p/<slug> link and that omitting it triggers listing. The description restates this plus the workflow of reusing the slug with open_in_studio, but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (fetches/lists) and resource (kernelCAD Studio project / signed-in user's saved projects), and explicitly names the sibling it differs from (list_my_projects, open_in_studio, get_model_mesh, get_latest_render). An agent can distinguish the two modes and route correctly without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use for both modes: pass `slug` to fetch, OMIT it to list, and it names the preferred alternative for listing ('prefer list_my_projects'). It also states the downstream workflow (edit then open_in_studio with the same slug) and gives a negative instruction ('do NOT call get_model_mesh or get_latest_render for interactive paint').

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.