Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

add_center_marks

Adds center marks to every hole and round edge in a SOLIDWORKS drawing view that lacks one, sizing them by the drawing's drafting standard and leaving existing marks unchanged.

Instructions

Add centre marks to a drawing view: every hole and round edge in it without one gets a single mark, sized by the drawing's drafting standard. Marks already there (a template can add them when the view is made) are left as they are. Returns each new mark's centre in view coordinates (mm, as list_drawing_views gives them) with the edges it marks.

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>"
    },
    "name": "add_center_marks"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYesView name from list_drawing_views

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/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 well: it discloses that only unmarked holes/round edges are affected, that existing marks are untouched, that sizing follows the drawing's drafting standard, and that results are returned in view coordinates in mm consistent with list_drawing_views. It does not mention permissions or failure modes, keeping it short of a 5.

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?

Three tight sentences, front-loaded with the action and scope, then the idempotency caveat, then the return value. No filler and each sentence contributes distinct information.

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 single-parameter tool with no output schema, the description covers what it does, what it skips, how marks are sized, and what the return value contains and in what units. Nothing an agent needs to invoke it correctly is missing.

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?

Only one parameter exists and schema coverage is 100%, with the schema already stating 'View name from list_drawing_views.' The description adds no further meaning about the view argument, so the baseline 3 applies.

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 ('Add centre marks to a drawing view') and narrows the scope precisely to 'every hole and round edge in it without one.' An agent can tell this apart from a generic centerline tool, though it never names a sibling to contrast with.

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?

Implies when it is appropriate by noting that marks already present (e.g. from a template) are left alone, which tells the agent the call is safe to repeat. However, it gives no explicit when-to-use versus alternatives such as add_centerlines, leaving that inference to the agent.

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