Skip to main content
Glama

Add Sketch Geometry

add_sketch_geometry

Append lines, circles, arcs, or points to a sketch and return assigned indices for constraint building.

Instructions

Append geometric primitives to a sketch.

items is a list of dicts:

  • {type: 'line', start: [x,y], end: [x,y], construction?: bool}

  • {type: 'circle', center: [x,y], radius: float}

  • {type: 'arc', center: [x,y], radius, start_angle, end_angle} (radians)

  • {type: 'point', pos: [x,y]} Returns {indices: [...]} — Sketcher-assigned indices for use in constraints.

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

Input Schema

NameRequiredDescriptionDefault
itemsYes
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.1/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=false, so the safety profile is covered. The description adds real value beyond that: 'Append' clarifies additive (not replace) semantics, and the stated return shape ({indices: [...]}) tells the agent what to do next. It omits error behavior, coordinate units, and ordering guarantees, so not 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?

Front-loaded one-line purpose, then a scannable per-type spec list, then the return value. Every line earns its place; nothing is repeated from the schema or annotations.

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?

Complete for a mutation tool: append semantics, full primitive grammar, and the return contract are all present, and annotations cover safety. The remaining gap is that 'sketch' is never identified as a handle vs. name, and no coordinate units are stated for x/y.

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

Parameters5/5

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

Schema coverage is only 33% and the items array is untyped ({}), so the description carries the burden — and does: it enumerates each primitive shape (line, circle, arc, point) with exact field names, the optional construction flag, and the radians unit for angles. This adds substantial meaning the schema does not provide; only the sketch handle type is left implicit.

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 — 'Append geometric primitives to a sketch' — which is precise enough to separate it from add_sketch_constraint and add_sketch_external. It never names those siblings or explicitly contrasts with them, so it falls just short of a 5.

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 only implied: the return-value note about 'use in constraints' hints at the geometry-then-constrain workflow, but the description never says when to call this versus add_sketch_external, nor that make_sketch must precede it. No exclusions or prerequisites are given.

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