Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

tab

Creates a merged sheet-metal feature from a closed sketch on a flat face using the part's thickness and returns the feature and added volume.

Instructions

Add a tab to a sheet metal part: a closed sketch drawn on the sheet's flat face (it may overlap the part) becomes sheet of the part's thickness, merged into the part. Returns the feature and the volume added. Refused while flattened.

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": {
      "sketch": "<sketch>"
    },
    "name": "tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
sketchYesName of a closed sketch on a flat face of the sheet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that the resulting material is merged into the part, that the sketch may overlap existing material, that it returns the feature and volume added, and that it is refused in the flattened state. It omits whether the operation is reversible and what the failure looks like.

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: the operation, the return value, and the blocking condition. Nothing is padded and the core action is front-loaded.

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 one-parameter mutation with no output schema, the description covers input requirements, result merging behavior, what is returned, and the refusal condition. The term 'flattened' is unexplained and permissions/irreversibility are unaddressed, leaving minor gaps.

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 the single 'sketch' parameter is already documented. The description adds only marginal meaning beyond the schema — the 'may overlap the part' note — and otherwise restates the requirement of a closed sketch on a flat face.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Add a tab to a sheet metal part') and defines the operation geometrically: a closed sketch on a flat face becomes material of the part's thickness, merged in. It does not name or contrast a sibling tool, so an agent must infer the boundary from the domain wording.

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

Usage Guidelines3/5

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

Usage is implied by the geometric description (you need a closed sketch on a flat face) and one precondition is stated ('Refused while flattened'), but there is no explicit when-to-use framing and no alternatives are suggested for related sheet metal operations.

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