Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

get_sheet_metal_info

Reads active SOLIDWORKS sheet metal settings—thickness, bend radius, K-factor, bends, flat pattern size, piece count and flattened state—without modifying the part.

Instructions

Read the active part's sheet metal settings (read only): thickness, default bend radius, K-factor, the bends (inside radius, angle in degrees and width of each), flat pattern size (bounding box, largest first), number of flat pieces, and whether the part is flattened now. A part with no unsaved changes is measured on a temporary copy, so the document is untouched and stays unmodified (measured_on = copy); an already modified part is measured in place, the flat pattern shown (or hidden) for a moment and then put back exactly as it was (measured_on = document). Refused on a part that is not sheet metal, and on assemblies and drawings.

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

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for the sizes in the result (mm, cm, m, inch or ft)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it declares read-only intent, explains that an unmodified part is measured on a temporary copy leaving the document untouched, and that a modified part is measured in place with the flat pattern briefly toggled and restored exactly. The measured_on values tie this behavior to observable output, which is unusually complete disclosure for a mutation-adjacent operation.

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 key scope statement is front-loaded and every clause carries information (fields, side-effect model, refusal cases). It is dense but reads as one long sentence, which slightly hurts scanability rather than clarity.

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?

There is no output schema, yet the description effectively documents the return contents and even the measured_on indicator, and it covers the failure modes. For a read-only, single-optional-parameter tool this leaves nothing an agent would need before calling it.

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% and the single optional 'unit' parameter is fully documented in the schema (mm, cm, m, inch, ft). The description never mentions the unit parameter or its effect on returned sizes, so it adds nothing beyond the schema; baseline 3 applies.

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 opens with a specific verb and resource ('Read the active part's sheet metal settings'), then enumerates exactly the fields returned (thickness, bend radius, K-factor, bends, flat pattern size, piece count, flattened state). This clearly separates it from siblings like convert_to_sheet_metal or get_cut_list without ambiguity.

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 explicit negative conditions: refused on parts that are not sheet metal, and on assemblies and drawings, which prevents misuse. It does not name a sibling alternative for those cases, so it stops short of full when-to-use routing.

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