Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

forming_tool

Presses a design-library shape such as a dimple or louver into a flat sheet metal face at a point, with flip and rotation controls for correct placement.

Instructions

Press a forming tool from the installed design library (e.g. dimple, louvers/louver, lances/...) into a flat face of a sheet metal part at a point. It pushes away from that face; flip presses from the other side, toward it. rotation turns it on the face. An unknown name is refused with the list. Returns the feature and its height. 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": {
      "tool": "<tool>",
      "point": "<point>"
    },
    "name": "forming_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNoPress the other way
toolYesLibrary name, e.g. dimple or embosses/dimple
unitNomm, cm, m, inch or ft
pointYesA point on a flat face of the sheet, where the tool goes
rotationNoRotation on the face in degrees

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses direction of deformation ('pushes away from that face'), the effect of flip and rotation, an error contract ('An unknown name is refused with the list'), a state precondition ('Refused while flattened'), and the return value ('the feature and its height'). It stops short of stating whether the operation is reversible or what document state must be active.

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?

Four short sentences, front-loaded with the core action, then direction semantics, error behavior, and return value in descending importance. The only blemishes are the truncated example list ('lances/...') and the clipped fragment 'Refused while flattened', which reads tersely but is understandable.

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 5-parameter mutation with a nested point object and no output schema, the description covers the essential unknowns: direction, error handling, preconditions, and the return value. Missing pieces are modest — whether an active sheet metal document is required and how the unit parameter interplays with the point coordinates.

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 the baseline is 3, but the description genuinely adds meaning: it explains that flip presses toward the face from the other side (the schema only says 'Press the other way'), that rotation turns the tool on the face, and that an invalid 'tool' name yields the valid list. Only 'unit' goes without any narrative elaboration.

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 gives a specific verb and resource: press a forming tool from the installed design library into a flat face of a sheet metal part at a point. It even enumerates library-name shapes (dimple, louvers/louver, lances/...), which tells an agent exactly what class of operation this is and what the 'tool' argument looks like.

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?

The operating context is implied rather than stated as a rule: it must be a sheet metal part with a flat face, and it is 'Refused while flattened', which is a useful precondition. However, the description never frames when to pick this over another approach (e.g. a hole, cut, or form feature created elsewhere), so guidance is left to inference.

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