Skip to main content
Glama

kernelcad

by com.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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoThe project slug from a listing or a /p/<slug> Studio link. Omit to list the signed-in user's saved projects.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoWhether the read succeeded.
codeNoFetch mode: the full .kcad source.
slugNoFetch mode: the project slug.
titleNoFetch mode: the project title.
assetsNoComplementary files keyed by source-relative path.
privacyNoFetch mode: the project privacy.
versionNoFetch mode: the project version.
projectsNoList mode (no slug): the user's saved projects.
parametersNoFetch mode: the model's editable parameters.
updated_atNoFetch mode: last-updated timestamp.

Schema Changelog

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

  1. Changed1 schema field changed
    • addedOutput schema / properties / assets
      Added value: +{
+  "additionalProperties": true,
+  "description": "Complementary files keyed by source-relative path.",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed2 schema fields changed
    • 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"
-]
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

The description adds value beyond annotations by detailing that it fetches the full .kcad source and metadata, that updating the same slug live updates the user's open tab, and that private projects require OAuth. Annotations already declare readOnlyHint and destructiveHint, so the description complements them without contradiction.

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 four sentences long, each providing unique information. It could be slightly more concise, but it is well-structured and front-loaded with the main purpose.

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's dual mode (fetch vs list) and dependencies (OAuth, output structure), the description covers essential context. The presence of an output schema reduces the need to describe return values, so the description is adequately complete.

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?

With 100% schema description coverage, the baseline is 3. The description adds context about the slug's origin (from a listing or /p/<slug> link) and the behavior when omitted, which is helpful but not extensive.

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 it fetches a specific project or lists saved projects, distinguishing between the two modes based on the slug parameter. It directly addresses the verb 'get' and the resource 'project', and provides specific use cases like reopening a saved project or browsing.

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 explicitly states when to use the tool (to reopen a saved project or browse saved projects) and provides context about OAuth requirements for private projects and listing mode. While it doesn't explicitly mention when not to use it or list alternatives, it gives clear guidance on usage.

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