Skip to main content
Glama
solidworks-mcp

solidworks-mcp

create_axis

Creates a reference axis from a cylindrical or conical face, straight edge, or two planes for circular patterns, revolves, or angled planes.

Instructions

Creates a reference axis, e.g. for a circular pattern, a revolve or an angled plane: face_point = a point on a cylindrical or conical face (its axis, e.g. the axis of a hole); edge_point = a point on a straight edge; or planes = two plane names / "front", "top", "right" (their intersection). name renames it. Returns its name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_axis"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
planesNo
edge_pointNo
face_pointNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the description only needs to add context. It adds the geometric semantics of what is created and that the resulting axis name is returned, but does not say whether the axis persists in the document, whether calling twice creates duplicates (relevant given idempotentHint=false), or what happens with conflicting names.

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-loaded with the purpose, then a compact semicolon-delimited breakdown of each parameter. The parameter clause is dense and reads as a run-on, but every clause conveys distinct information and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not required (it covers it anyway). The main gap is that with four optional parameters and no required ones, the definition never states that exactly one construction mode must be supplied, nor what error results if none or several are given — a meaningful omission for a creation tool.

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 description coverage is 0%, so the description carries the full burden and it largely does: it defines the meaning of face_point, edge_point, planes, and name, including that planes accepts canonical names like 'front'/'top'/'right'. It stops short of saying that face_point/edge_point are coordinate triples, so the numeric array shape remains inferred.

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 ('Creates a reference axis') and names concrete downstream uses (circular pattern, revolve, angled plane), so the agent knows what it produces. It does not explicitly contrast with the close sibling create_plane, leaving that differentiation implicit.

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?

Explains the three construction modes and what geometric input each requires ('face_point = a point on a cylindrical or conical face', 'edge_point = a point on a straight edge', 'planes = two plane names / front, top, right'), which effectively tells the agent how to choose inputs. It gives no explicit when-not-to-use guidance or routing to sibling creation tools.

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