Skip to main content
Glama

Add Sketch External

add_sketch_external

Projects external edges, faces, or vertices into a sketch as construction geometry so constraints stay anchored to upstream features and survive dimensional edits.

Instructions

Project an external edge/face/vertex into a sketch as construction geometry.

ref: {handle, edge: tag|'EdgeN'} (or face/vertex variant; or {handle, tag} where tag is e_/f_ prefixed). The projected element gets a negative geom index so subsequent constraints can reference it. Use this to make a sketch that stays anchored to upstream geometry (e.g. a hole 5mm from a tagged edge that survives pad-length edits).

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": {
      "sketch": "<sketch>",
      "ref": "<ref>"
    },
    "name": "add_sketch_external"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
sketchYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the projected element receives a negative geom index so later constraints can reference it, and the reference is bound to upstream geometry. That is exactly the kind of state-mutation consequence the readOnlyHint=false/destructiveHint=false annotations cannot express. It does not cover what happens on a stale or unresolvable reference.

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-loads purpose in the first sentence, then ref syntax, then behavioral note, then rationale — a sensible ordering. The parenthetical ref alternatives are dense and slightly opaque, but no sentence is padding.

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 mutation tool with no output schema, the description covers what gets created (negative geom index) and why it matters. Gaps remain around preconditions (must the sketch be open/active) and error behavior for unresolved handles, but nothing essential to calling it is missing.

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 coverage is only 33% and `ref` is a free-form object with additionalProperties=true and no schema description, so the description must compensate, which it largely does by spelling out {handle, edge: tag|'EdgeN'}, the face/vertex variant, and the {handle, tag} e_/f_-prefix form. The face/vertex variant is only alluded to rather than named, leaving some key-name ambiguity.

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 and outcome: 'Project an external edge/face/vertex into a sketch as construction geometry.' This clearly distinguishes it from the sibling add_sketch_geometry, which adds new geometry rather than projecting existing upstream geometry.

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 an explicit 'Use this to...' condition with a concrete motivating example (a hole 5mm from a tagged edge that survives pad-length edits), so the agent knows when projecting is preferable. It stops short of naming the alternative tool (add_sketch_geometry) or stating when not to use 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