Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

create_new_part

Create an empty SOLIDWORKS part from the default template and make it the active document; the result reports the template's units and standard.

Instructions

Create an empty part from the default template and make it the active document; the result names the template's units and standard.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description still discloses a real side effect — the new part becomes the active document — and pre-announces the return content (template units and standard) despite there being no output schema. It stops short of covering failure modes (missing default template) or session/connection requirements.

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

Conciseness5/5

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

A single sentence with the creation action front-loaded, followed by side effect and return value separated by a semicolon. No filler or redundant restatement of the title.

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?

For a no-parameter creation tool with no annotations and no output schema, the description carries the important behavioral facts (template source, active-document side effect, returned metadata). Only environmental prerequisites and error conditions are left unstated.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty, so there is nothing about arguments to document; per the baseline this scores 4. The description correctly frames that all behavior is driven by the default template rather than by user input.

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?

Specific verb plus resource: "Create an empty part from the default template." It also states the resulting state ("make it the active document") and what the result reports (units and standard), which clearly separates it from create_new_assembly or create_drawing without needing to name them.

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?

Usage is only implied by the verb; there is no explicit statement of when to prefer this over create_new_assembly or when not to call it. It also omits prerequisites such as whether a session must already be connected (a connect_solidworks sibling exists) or whether an existing open document is affected.

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

Deploy Server

Other Tools