Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Balloons

add_balloons

Numbers parts in an assembly drawing view with one balloon per part, carrying BOM item numbers for clear component labeling.

Instructions

Number the parts in a drawing view with balloons, one per part.

Use it on an assembly drawing, with a BOM (insert_bom_table): the balloons carry the BOM's item numbers. Works best on an exploded view (create_drawing_view with exploded). Needs: an open drawing with a view of an assembly. Changes: adds balloons around the view. Returns: balloons with the view, layout, count and the items shown. A view that isn't there fails as not_found.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYes`view_name` is required; `layout` is `square`.

Output 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?

The annotations already establish that this is a non-read-only, non-idempotent, non-destructive operation. The description adds useful behavioral context beyond that: prerequisites, the fact that balloons are added around the view, return fields, and the `not_found` failure mode.

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?

The description is front-loaded and efficiently organized into purpose, usage, prerequisites, effects, returns, and failure behavior. It is slightly dense but contains little waste.

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?

Given the existing output schema and annotations, the description is complete enough for correct invocation. It covers prerequisites, expected context, side effects, return fields, and a key failure mode.

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 description coverage is 100%, so the input schema already documents `view_name` and `layout`. The description adds indirect meaning by requiring an assembly view and stating one balloon per part, but it does not significantly elaborate on parameter format 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 states a specific verb and resource: number parts in a drawing view with balloons, one per part. It also makes the assembly-drawing context explicit, so an agent can distinguish this from generic annotation tools.

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?

It clearly says to use this on an assembly drawing with a BOM and that it works best on an exploded view. It does not explicitly say when not to use it or name alternative balloon/annotation approaches, but the intended context is strong.

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