Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sketch_mirror

Mirrors sketch entities across a construction line in an open SolidWorks sketch using specified entity points and a point on the mirror line.

Instructions

Mirrors sketch entities of the open sketch about a construction line (sketch_line with construction=True). entity_points: [[x, y], ...] one point on each entity to mirror; mirror_line_point: [x, y] a point on the construction line. 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": {
      "entity_points": "<entity_points>",
      "mirror_line_point": "<mirror_line_point>"
    },
    "name": "sketch_mirror"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_pointsYes
mirror_line_pointYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare it is a non-readonly, non-idempotent, non-destructive mutation, and the description adds the useful note 'Replaces the selection,' which is genuine context beyond the annotations. It does not address the non-idempotency risk (whether re-running duplicates mirrored geometry) or whether the mirrored copies become new unconstrained entities.

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?

Densely front-loaded: the operation comes first, then per-parameter semantics, then the selection side effect. Some compression is awkward (the parameter notes run together without clear delimiters), but no sentence is wasted.

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?

Both parameters are documented and an output schema exists, so return values need no explanation. For a two-parameter mutation the definition is close to sufficient, with only the non-idempotency behavior and the relationship to the 'mirror' sibling left unaddressed.

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 bears full responsibility, and it delivers: it gives the exact array shape for entity_points ([[x, y], ...]), explains that each entry is one point on an entity to mirror, and defines mirror_line_point as [x, y] on the construction line. What is left implicit is how a single point identifies an entire entity.

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?

States a specific verb and resource: 'Mirrors sketch entities of the open sketch about a construction line,' and scopes it to the open sketch plus a construction=True line. It does not explicitly distinguish itself from the 'mirror' sibling, so an agent must infer that distinction from context rather than instruction.

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 precondition (a construction line must already exist) is clearly stated, which is real usage guidance. However, there is no explicit when-to-use versus alternatives such as 'mirror' or 'sketch_linear_pattern', and no statement of what happens if the sketch is not open or no construction line exists.

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