Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

add_balloons

Adds numbered item balloons to an assembly drawing view, one per component and matched to the bill of materials, with optional layout placement and default isometric view.

Instructions

Add item balloons to a view of an assembly in the active drawing: one per component, numbered as in the bill of materials (add_bom_table). Default view: the isometric view, if there is one. SolidWorks balloons each item once per sheet, so a second view only gets balloons for items the first one did not show. Returns the item numbers.

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

Input Schema

NameRequiredDescriptionDefault
viewNoA view of the assembly (default: the isometric view, else the first view)
layoutNoWhere the balloons go around the viewsquare

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 carries the behavioral burden and does well: it discloses the default-view fallback, the SolidWorks once-per-sheet dedup rule ('a second view only gets balloons for items the first one did not show'), and that item numbers are returned. It omits prerequisite failures (e.g. what happens with no drawing active or no BOM present) and does not say whether balloons are written destructively to the document.

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?

Three compact sentences, front-loaded with the primary action, then defaults, then the per-sheet constraint and return value. No filler and every clause carries information the agent needs.

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 two-parameter optional-argument tool with no output schema, it covers defaults, cross-tool dependency (add_bom_table), repeated-invocation semantics, and return values. Only error/precondition behavior is left implicit.

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%, so both parameters are already documented, including the same six-value enum and default. The description adds only the isometric default for 'view', which is redundant with the schema, and says nothing extra about how 'layout' positions balloons (spacing, offsets, ordering).

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 ('Add item balloons to a view of an assembly in the active drawing') and immediately clarifies the unit of work ('one per component, numbered as in the bill of materials'), which cleanly separates it from the sibling add_bom_table that produces the numbering.

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 gives clear operating context: the default view (isometric if present, else the first view) and the relationship to add_bom_table. What it does not do is state explicit exclusions or when to prefer an alternative, though the once-per-sheet rule effectively tells the agent that calling it repeatedly on multiple views is the intended pattern.

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