Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

delete_drawing_dimension

Deletes a dimension from a SOLIDWORKS drawing view by name, removing it from the drawing only while the model dimension stays in the part.

Instructions

Delete a dimension from a drawing view by the name list_drawing_views(view=...) gives, e.g. RD1. Only the drawing changes; the model dimension stays in the part.

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": {
      "view": "<view>",
      "dimension": "<dimension>"
    },
    "name": "delete_drawing_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYesName of the view the dimension is in
dimensionYesDimension name, e.g. RD1 or D1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the key trait that only the drawing changes while the model dimension persists in the part, which is genuinely useful. However, it is silent on irreversibility/undo, whether deletion fails or no-ops on an unknown name, and required document state, leaving meaningful gaps for a mutation.

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 short sentences, front-loaded with the action and target, followed by the scope caveat. No filler and nothing buried.

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 mutation with no output schema, the description covers purpose, name sourcing, and the model-vs-drawing effect. It could add failure behavior on invalid names or document-state prerequisites, but nothing essential is misleadingly absent.

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 both parameters are already documented, establishing a baseline of 3. The description adds value beyond the schema by explaining where the dimension name must come from (list_drawing_views) and reinforcing the expected format with RD1.

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 and resource ("Delete a dimension from a drawing view") and scopes it to drawing-view dimensions, which separates it from model-level siblings like delete_feature or delete_equation. The example identifier (RD1) makes the target concrete.

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?

Explicitly routes the agent to list_drawing_views(view=...) as the way to obtain a valid dimension name, which is clear usage context. It stops short of naming when-not-to-use cases (e.g. model dimensions belong to a different tool), so it is not a full 5.

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