Skip to main content
Glama
solidworks-mcp

solidworks-mcp

delete_sketch_entity

Destructive

Delete sketch entities by specifying one [x, y] point on each in sketch coordinates; their relations and dimensions are removed with them.

Instructions

Deletes sketch entities of the open sketch: one [x, y] point on each, in sketch coordinates. Their relations and dimensions are deleted with them.

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": {
      "points": "<points>"
    },
    "name": "delete_sketch_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered; the description earns credit for adding the cascade consequence that attached relations and dimensions are removed with the entities. It still omits practical behavior such as matching tolerance when a supplied point misses an entity, or what happens when several points resolve to the same entity.

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?

Two tight sentences: the operation and its scope come first, the input format second, the side effect third. No filler or redundant restatement of the tool name.

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?

With annotations covering destructiveness and an output schema present, the description supplies the two things an agent cannot infer: the point-based selection format and the cascading deletion of relations and dimensions. Precondition is stated implicitly rather than explicitly, and lookup-failure behavior is unaddressed, so it stops short of fully complete.

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% and the single parameter is an untyped nested array of numbers, so the description carries the full burden — it resolves this by stating each entry is one [x, y] point in sketch coordinates. That converts an opaque structure into an unambiguous input format. It remains silent on coordinate units, tolerance, and whether partial failure is possible.

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 uses a specific verb and resource ('Deletes sketch entities') and scopes it to 'the open sketch', which is enough for an agent to distinguish it from broad deletion siblings like delete_feature or delete_equation. It does not explicitly name or contrast with those siblings, keeping it just below a 5.

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 phrase 'of the open sketch' implies a precondition (a sketch must be active) but never states it as a requirement or tells the agent what to do if no sketch is open. There is no explicit guidance on when to use this versus delete_feature or edit_sketch, leaving routing to inference.

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