Skip to main content
Glama

Make Sketch

make_sketch

Creates a sketch in a Body attached to an origin or datum plane, returning its handle and name for downstream modeling.

Instructions

Create a sketch in a Body, attached to a plane.

plane: 'XY' | 'XZ' | 'YZ' for origin planes, or a datum-plane handle. Returns {handle, name}.

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": {
      "body": "<body>"
    },
    "name": "make_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
nameNoSketch
planeNoXY
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the return shape ("Returns {handle, name}"), which is useful since there is no output schema, but it does not say whether the sketch is left open and must be closed before padding, or what happens on name collisions.

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?

Three short blocks in a logical order: purpose, plane values, return shape. Nothing is padded, though the fragmentary style (bare 'plane:' line) is terser than ideal for readability.

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

Completeness3/5

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

For a 4-parameter creation tool with no output schema and sparse schema descriptions, the definition covers the essentials but omits workflow context an agent needs — notably whether the sketch must be closed (close_sketch) before pad/revolve, and whether the body must already exist.

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?

With only 25% schema coverage and no enums, the description carries real weight: it supplies the allowed plane values ('XY' | 'XZ' | 'YZ') or a datum-plane handle, and frames body as the owning Body. Name and workspace get no description treatment, but the plane semantics — the parameter most likely to be called wrong — are fully covered.

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 ("Create a sketch") plus the scope constraint ("in a Body, attached to a plane"), which separates it from siblings like add_sketch_geometry or close_sketch. It does not name those siblings explicitly, so differentiation is inferred rather than stated.

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?

The requirement for a body and a plane implies this is the sketch-creation step that precedes add_sketch_geometry/add_sketch_constraint/close_sketch, but no alternative is named and no when-not condition is given. Usage is implied, not taught.

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