cadkit

by saltyeg

Overview Schema Source Related Servers Discussions Admin

Python

Remote

cad_document_create

Create a new Onshape document to start parametric part modeling. Returns the document ID and main workspace ID.

Instructions

Create a document and return documentId + the Main workspaceId.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "cad_document_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jun 24, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations exist, so the description must carry the burden. It only reveals the return value but omits side effects (e.g., mutation), permissions, idempotency, or error conditions. For a creation tool, this is insufficient.

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?

A single sentence, no superfluous words. It is efficient but could be slightly more structured with clarity on parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 2 parameters (one required), no output schema, and many sibling tools, the description lacks detail about parameter usage and return value structure. It is too minimal for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description adds no meaning to the parameters 'name' or 'description'. It does not explain format, constraints, or purpose beyond the 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?

The description clearly states the action (create) and resource (document), and specifies the return value (documentId + Main workspaceId). It distinguishes from sibling tools like cad_part_studio_create which creates a different resource.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like cad_part_studio_create. No prerequisites or context provided.

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