Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

draw_centerline

Add a construction centerline to an open sketch so it can serve as a revolve axis or mirror line for symmetric relations.

Instructions

Add a centerline (a construction line) to the open sketch. It is the axis for revolve_sketch and the mirror line of a 'symmetric' relation.

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "draw_centerline"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesX of one end of the axis
x2YesX of the other end
y1YesY of one end of the axis
y2YesY of the other end
unitNomm, cm, m, inch or ft

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the result is a construction line added to the open sketch and that it serves as an axis or mirror line, but it does not describe side effects, failure behavior when no sketch is open, or whether the line is selectable or editable afterward.

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?

The description is two compact sentences with no wasted wording. The core purpose is front-loaded, followed by the geometric roles that help the agent decide when to use it.

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 simple sketch-construction tool with a fully documented five-parameter schema and no output schema, the description supplies the essential purpose, prerequisite, and use cases. It is nearly complete, though it could say more about mutation behavior or post-creation state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already documents x1, y1, x2, y2, and the unit parameter. The description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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?

The description uses a specific verb and resource: 'Add a centerline (a construction line) to the open sketch.' It also distinguishes the centerline's geometric role as an axis for revolve_sketch and a mirror line for symmetric relations, so the agent can tell what this tool creates and how it differs from generic line drawing.

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?

It gives clear context for use: the sketch must be open, and the centerline is intended for revolve_sketch axes and symmetric-relation mirror lines. It does not explicitly exclude alternatives such as draw_line or add_centerlines, but the intended use cases are clear.

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