Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

edit_sketch

Add, edit, or delete sketch geometry and constraints with automatic Coincident/H/V constraining and undo support.

Instructions

Add/edit/delete Sketch geometry & constraints with automatic Coincident/H/V constraining (undoable).

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_name": "<sketch_name>"
    },
    "name": "edit_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_nameNo
geometriesNo
constraintsNo
sketch_nameYes
auto_constrainNo
fillet_cornersNo
update_constraintsNo
external_geometriesNo
toggle_constructionNo
delete_geometry_indicesNo
delete_constraint_indicesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds real behavioral context beyond them: automatic Coincident/Horizontal/Vertical constraining applied by default, and that the operation is undoable. It does not say whether an edit replaces or merges existing geometry, which matters for a non-idempotent tool. Note a tension: the description advertises 'delete' while destructiveHint=false, though 'undoable' partially reconciles it.

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?

A single front-loaded sentence with the core verb set first and behavioral qualifiers in parentheses; no filler. It is efficient, though the brevity is partly under-specification rather than disciplined concision.

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

Completeness2/5

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

For an 11-parameter mutation tool that accepts free-form geometry and constraint objects, one sentence is not enough: the agent cannot know the required element keys, index conventions for deletions, or the interaction between auto_constrain and explicitly supplied constraints. The output schema existence reduces the need to describe return values, but the call-shape guidance is still missing.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters, and most are arrays of arbitrary objects (geometries, constraints, fillet_corners, external_geometries) whose element shape is completely undocumented in either schema or description. The description only gestures at two behaviors ('automatic Coincident/H/V constraining' mapping loosely to auto_constrain, and 'delete' covering the two delete_*_indices params), leaving update_constraints, toggle_construction and fillet_corners unexplained.

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?

The description uses specific verbs (add/edit/delete) against a specific resource (Sketch geometry & constraints), which is far clearer than a generic 'edit' tool. It separates itself reasonably from create_sketch by framing itself as the mutation surface for an existing sketch, though it never names that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says this operates on an already-existing sketch versus create_sketch, nothing says whether pad_sketch/pocket_sketch must come after, and no prerequisites (active document, body context, sketch edit mode) are stated. The only implied usage is the verb 'edit', which the agent has to infer.

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