Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sketch_trim

Destructive

Trim a sketch entity at the clicked X/Y point back to its nearest intersections, removing the pointed segment or deleting the entity if it crosses nothing.

Instructions

Trims the sketch entity through (x, y) in the open sketch back to its nearest intersections with other entities: the piece you point at is removed (like Trim to closest). An entity that crosses nothing is deleted entirely. Replaces the selection.

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": {
      "x_mm": "<x_mm>",
      "y_mm": "<y_mm>"
    },
    "name": "sketch_trim"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_mmYes
y_mmYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description goes further by specifying exactly what is destroyed (the pointed-at piece between nearest intersections), what happens to isolated entities (full deletion), and a side effect on the current selection. It does not mention undo/reversibility or behavior on entities split into multiple segments, which is the remaining gap.

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?

Front-loads the core action and scope, then adds the two clarifying edge cases in short clauses. The parenthetical '(like Trim to closest)' is somewhat redundant but cheap and aids recognition; overall tight with no wasted sentences.

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 destructive edit tool with an output schema present, the description covers prerequisite, cutting rule, edge case, and selection side effect — enough to call it correctly. Missing only secondary details such as reversibility and behavior when multiple entities share the pick point.

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 0%, so the description must carry the parameter meaning — and it does: (x, y) is the pick point that identifies which piece of the entity is removed, not an endpoint of the result. Units (mm) are only conveyed by schema titles, not the description, which keeps it from a 5.

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?

States a specific verb (trims) on a specific resource (sketch entity through a point in the open sketch) and defines the exact cut criterion (nearest intersections with other entities). It also distinguishes the degenerate case — an entity with no crossings is deleted entirely — so an agent understands this is not simply a delete or a trim-by-distance operation.

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?

Implies the prerequisite that a sketch must be open and that the point must lie on the entity to be trimmed, which is the key condition for correct invocation. It does not name an explicit alternative (e.g. delete_sketch_entity) for the case where the user wants plain removal, so the when-not guidance is only partial.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.