Stop the active SOLIDWORKS macro recording session and save the generated macro code to a file for reuse or editing.
Stop macro recording and save the recorded macro.
This tool stops the active recording session and saves the generated macro code to a file.
| Name | Required | Description | Default |
|---|---|---|---|
| input_data | Yes | The input data value. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It discloses that the tool stops recording and saves to a file, indicating a destructive write operation. However, it omits details like whether recording must be active or error conditions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two sentences that are front-loaded and directly state the tool's action. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has an output schema and a simple parameter structure. The description covers the basic action but lacks context like prerequisites (recording must be active) or error handling. It is adequately complete given the simplicity, but could be improved.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter input_data has a minimal description in the schema. The tool description adds no extra meaning beyond the schema, meeting the baseline but not exceeding it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool stops macro recording and saves the recorded macro, with a specific verb and resource. It distinguishes itself from sibling tools like start_macro_recording and execute_macro.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit guidance on when to use this tool versus alternatives, such as execute_macro or analyze_macro. It only implies usage after starting recording but lacks exclusions or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.