Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

add_centerlines

Adds centrelines to a drawing view or to every view on the active sheet, placing them on cylinders, cones and side-seen slots that lack one, and reports the counts added.

Instructions

Add centrelines to a drawing view, or with no view to every view on the active sheet: SolidWorks puts one on every cylinder, cone and slot seen from the side that has none (a template can add them when the view is made). Returns how many were added and how many the view now has; SolidWorks gives no position for a centreline.

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": "add_centerlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoView name from list_drawing_views. Leave out for every view on the active sheet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the selection rule (only cylinders, cones and slots seen from the side that lack a centreline), the return values (count added and total now present), and a real limitation (SolidWorks reports no position for a centreline). That is exactly the behavioral context an agent needs before mutating a drawing.

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 verb and resource, and every clause carries information (scope default, selection rule, return values, limitation). The sentence chain is dense and slightly run-on with colons and semicolons, but nothing is wasted.

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

Completeness5/5

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

For a one-parameter mutation tool with no annotations and no output schema, the description covers scope, side effects, return shape, and a known API limitation. An agent has everything needed to call it correctly and interpret the result.

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 coverage is already 100% and the single 'view' parameter is documented as coming from list_drawing_views. The description restates the omission semantics ('Leave out for every view on the active sheet'), matching the schema, so it adds consistency but little new meaning. Baseline 3 applies.

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 ('Add') and resource ('centrelines') plus the target scope (a drawing view or every view on the active sheet). The parenthetical about which entities get a centreline further pins down exactly what the tool does, so an agent can distinguish it from siblings like add_center_marks.

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?

Gives clear context for both call modes: supply a view to target one, or omit it to cover the whole active sheet, and notes that a template can create centrelines at view-creation time instead. It stops short of explicitly saying when to prefer this over add_center_marks or when not to call it.

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