Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Rib

create_rib

Adds a rib from an open sketch line to stiffen a wall or shell interior; extends to adjacent walls and returns before/after volume data.

Instructions

Add a rib from a sketched line, stiffening a wall or the inside of a shell.

Sketch an open line where the rib goes (it can stop short of the walls; the rib extends to meet them), close the sketch, then call this with its name. It fails when the volume doesn't change. Needs: an open part and the rib sketch. Changes: adds a Rib feature. Returns: rib with name, sketch, thickness_mm, and volume_before, volume_after and volume_change (mm³).

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": "create_rib"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe rib. `sketch` and `thickness` (mm) are required; `both_sides` is on.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower, and the description still adds real context: preconditions, the volume-change failure mode, the fact that it adds a Rib feature, and the returned fields. The only gap is that it does not explain why the operation is non-idempotent or what state remains if it fails.

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?

Front-loads the purpose, then prerequisites, then failure mode, then effects and return shape – a sensible order with no filler. The trailing 'Returns:' enumeration duplicates the output schema and the mid-sentence line breaks make it slightly harder to scan.

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?

For a mutating feature-creation tool with a nested object schema and an output schema, the description covers preconditions, failure condition, side effects, and units. Nothing an agent needs to call it correctly is missing, especially since return details are also structured.

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?

Schema coverage is 100%, so a 3 would be the floor; the description earns more by explaining what the sketch parameter must contain ('an open line... it can stop short of the walls') and that thickness is in mm, which the schema alone states only tersely. The optional flags (both_sides, flip_material, normal_to_sketch) are left entirely to 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?

States a specific verb and resource ('Add a rib from a sketched line') plus the geometric intent ('stiffening a wall or the inside of a shell'), which separates it from generic feature tools like create_extrusion or create_shell. An agent can decide this is the rib tool without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear prerequisite workflow: sketch an open line, close the sketch, then call with its name, and notes the line may stop short because the rib extends to meet the walls. It also names a failure condition ('fails when the volume doesn't change') and required inputs ('an open part and the rib sketch'). It stops short of naming an alternative tool for the non-rib case, so not a 5.

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