A rate-limited MCP server that lets AI assistants create and inspect Onshape CAD
Server has 9 tools with complete schemas and descriptions. Naming follows verb_noun convention (list_, create_, get_, delete_, add_). Descriptions are present and contextual (avg ~150 chars), exceeding the 10-char minimum but below the 50-200 char LLM-optimized range for several tools. All parameters have type definitions and descriptions. However, output schemas are not documented, LLMs cannot predict response structure for chaining. Error handling is absent: no recovery guidance, no categorization of retryable vs fatal errors. Security concern: no mention of auth token injection or rate-limit handling despite the docstring claiming 'handles rate limiting transparently.' Tool descriptions lack dependency hints (e.g., 'Call list_documents first to get did') and some are generic ('Get detailed information about a specific feature'). Composition is sound, tools are single-responsibility and chainable (e.g., list_documents → get_document_info → list_features → get_feature_info). No batch variants offered. Baseline: 549 production tools average 18-char names (this server: 10-20 chars ✓), 194-char descriptions (this server: 80-250 chars, mostly ✓), 100% of A+ tools have documented return types (this server: 0% ✗).
Add a circle to an existing sketch. The sketch must have been created with create_sketch first. Multiple circles in the same sketch are supported. UNITS: All coordinates and dimensions in METERS. 1mm = 0.001, 1cm = 0.01. Example: Circle at origin, Ø10mm → center=(0,0), radius=0.005
Create a new Onshape document. Returns the document ID and workspace ID needed for subsequent operations.
Create a new 2D sketch on a plane in a Part Studio. This is the first step for creating 3D geometry. After creating a sketch, use add_circle, add_line, or add_rectangle to draw geometry, then use extrude to turn it into a 3D body. Planes: TOP (XY plane), FRONT (XZ plane), RIGHT (YZ plane). Add an offset in meters to create the sketch above/below the plane. UNITS: All distances are in METERS. Convert: 1 mm = 0.001, 1 cm = 0.01. Example: 50mm offset from TOP → offset=0.05
Delete a feature from a Part Studio. ⚠️ IMPORTANT: Features must be deleted in reverse order — children before parents. For example, delete an extrude before its sketch, and delete later features before earlier ones.
Get detailed information about an Onshape document, including its workspaces and elements (Part Studios, Assemblies, etc.). Use this to find the element IDs needed for working with parts and features.
No output schemas documented. LLMs cannot predict response structure, breaking tool chaining and forcing agents to guess field names for downstream calls.
No error handling guidance. Tools do not indicate what errors are retryable, what the LLM should do on failure, or how to recover. E.g., delete_feature could fail if dependencies exist, no guidance provided.
Missing dependency hints in descriptions. Tools like add_circle require sketch_id but do not explain how to obtain it (via create_sketch or list_features). Agents must infer multi-step workflows.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | <=2025-11-25 | v2 |
Get detailed information about a specific feature by its ID.
Search and list Onshape documents. Returns document names, IDs, and owners. Use this to find a document before working with its contents.
List all features in a Part Studio with their types, names, and suppression status. Features are the building blocks: sketches, extrudes, revolves, fillets, etc. Use this to understand the feature tree before modifying anything.
List all parts in a Part Studio. Returns part names, IDs, body types (solid/surface), mass, volume, and material. Use this to inspect what's in a Part Studio.
get_feature_info description is generic ('Get detailed information about a specific feature by its ID'). Does not explain what fields are returned, when to use it vs list_features, or what 'detailed' means.
No pagination support documented for list_* tools. list_documents accepts limit but no offset/cursor. Large result sets could exhaust context; no guidance on handling >50 results.