CADPilot

Overview Schema Source Related Servers Discussions Admin

set_anchors

Destructive

Define named anchors on CAD objects to mark positions and directions that persist, follow Placement, and record a modeling step; optionally replace or merge and use local/global coordinates.

Instructions

Define named anchors on an object. They persist with the document, move with its Placement, and the write becomes a modeling-session step.

Args:
    anchors: {name: {"pos": [x, y, z], "dir": [x, y, z] | null}}.
    replace: Replace all existing anchors instead of merging.
    coord_frame: local stores values as given; global converts them first, for global source coordinates.

Input Schema

TableJSON Schema

Name	Required	Default
`anchors`	Yes
`replace`	No
`doc_name`	Yes
`obj_name`	Yes
`coord_frame`	No	local

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.7Oct 7, 2026

removedInput schema / properties / with_screenshot

Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "With Screenshot"
-}

First observedv0.4.0Jul 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds genuinely new behavior — anchors persist with the document, follow its Placement, and the write is recorded as a modeling-session step (i.e., an undoable history artifact). The replace semantics clarify what actually gets destroyed.

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 one-line summary followed by a tight Args block; each arg line carries real information (nullable dir, conversion behavior). The middle sentence about persistence and session steps could be trimmed slightly but earns its place as the main behavioral disclosure.

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 5-parameter mutation tool with nested input, an output schema present, and full annotation coverage, the description supplies the mutation semantics (merge vs replace), the coordinate interpretation, and the durability/undo behavior. Remaining gaps are minor: no mention of error cases or what happens on a name collision beyond replace.

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 load, and it does: anchors is documented as a name→{pos, dir|null} nested structure, replace as wipe-vs-merge, and coord_frame as local-as-given vs global-converted. Only doc_name and obj_name are left undocumented, though their purpose is self-evident from the names.

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 ("Define named anchors on an object") and immediately characterizes the effect (persistence, attachment to Placement). It is clearly distinguishable from the sibling get_anchors by the write verb, though it never names that sibling or other neighbors explicitly.

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?

Usage is implied rather than stated: the merge-vs-replace note tells the agent which mode to pick, and the coord_frame note says when to use global ("for global source coordinates"). There is no explicit when-to-use-this-vs-alternatives guidance or prerequisite statement.

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