Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Generate VBA: Revolve

generate_vba_revolve
Read-onlyIdempotent

Generates VBA macro text that revolves a selected sketch with both-direction and thin-wall options. Use it when a standard revolve doesn't cover your options, then paste into the SolidWorks VBA editor.

Instructions

Write a VBA macro that revolves the selected sketch, with both-direction and thin-wall options.

Use it when create_revolve doesn't cover an option you need. The macro comes back as text for the SolidWorks VBA editor (Alt+F11); execute_macro runs only binary .swp files, so it can't run this directly. Read-only. Nothing runs in SolidWorks. Returns: vba_code, the parameters used and usage_instructions.

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": {
      "input_data": "<input_data>"
    },
    "name": "generate_vba_revolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe revolve. Give `angle` in degrees (it defaults to 0, a revolve of nothing); `sketch_name`, `axis_reference`, both-direction and thin-wall options have defaults.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / input_data / description
      Previous value: -"The input data value."New value: +"The revolve. Give `angle` in degrees (it defaults to 0, a\nrevolve of nothing); `sketch_name`, `axis_reference`, both-direction\nand thin-wall options have defaults."
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Adds real context beyond annotations: the output is text destined for the SolidWorks VBA editor (Alt+F11), and nothing executes as a side effect of generation. "Read-only. Nothing runs in SolidWorks." largely restates readOnlyHint/destructiveHint=false, which is the only redundancy; the delivery-format and downstream-execution facts are genuinely new.

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?

Five short sentences, front-loaded with purpose then conditional usage, then limitations, then return shape. No filler and no repetition of the title.

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

Completeness5/5

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

Covers purpose, alternative selection, execution caveat, and return fields; an output schema exists, so the one-line return summary is sufficient rather than redundant. Nothing an agent needs to invoke this correctly is missing.

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 coverage is 100% and the nested `input_data` description already documents defaults and the trap that `angle` defaults to 0 (a revolve of nothing). The description adds no parameter-level meaning beyond the schema, so this sits at the baseline for fully documented params.

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?

Opens with a specific verb and artifact: "Write a VBA macro that revolves the selected sketch," and names the two options (both-direction, thin-wall) that differentiate it from the plain revolve sibling. An agent can tell this apart from `create_revolve` and `execute_macro` 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?

Gives an explicit selection rule: use this when `create_revolve` doesn't cover a needed option. It also names the adjacent tool `execute_macro` and states the constraint that disqualifies it (binary .swp only), so the agent knows both the alternative and the dead end.

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