Skip to main content
Glama

edit_sketch

Reopen an existing sketch to edit dimensions, relations, or geometry without rebuilding the part.

Instructions

Reabrir un croquis existente para editarlo (agregar cotas, relaciones, o geometría) SIN reconstruir la pieza desde cero. Tras reabrir, las herramientas add_sketch_dimension / add_sketch_relation / create_line funcionan igual que en un croquis recién creado.

Uso típico CSWA: parametrizaste el Tool Block con cotas A/B/C; para ajustar otra arista, reabre el croquis con edit_sketch, agrega/edita, y sal con la siguiente operación (extrude/etc.) para fijar el cambio.

[en: Reopen an existing sketch for editing (dims, relations, geometry) without rebuilding the part. After reopening, add_sketch_dimension / add_sketch_relation / create_line behave as on a fresh sketch.]

Args: sketch_name: exact sketch name, e.g. "Croquis1".

Returns {name, editing: True}. The sketch stays OPEN — you MUST exit it (extrude_sketch or another sketch-consuming op) to lock the changes in; a rebuild while open will exit it on SW 2026 ES.

Related: create_sketch (new sketch); modify_dimension (drive a named cota without even reopening).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sketch_nameYes
Behavior5/5

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

No annotations provided, so description covers all behavioral aspects: no rebuild, effect on other tools, return value (editing=True), and caution about sketch staying open. Also mentions specific future behavior (SW 2026 ES). No contradictions.

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?

Bilingual text adds length, but each sentence adds value. Front-loaded with purpose, then usage, argument, return, warnings, and related tools. Minor redundancy due to translation but still effective.

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

Completeness5/5

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

Despite no annotations or output schema, the description covers all essential information: purpose, usage, parameter, return, behavior, warnings, and related tools. Nothing significant is missing.

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?

The schema has 0% description coverage, but the description adds the parameter's meaning: exact sketch name with an example ('Croquis1'). This fully compensates for the lack of schema description.

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?

The description clearly states the verb (reopen/edit), resource (sketch), and scope (without rebuilding). It distinguishes from siblings like create_sketch and modify_dimension, making the tool's purpose unambiguous.

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

Usage Guidelines5/5

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

Explicit when-to-use (editing existing sketch) and when-not-to-use (alternatives like modify_dimension for dimensions). Includes a typical CSWA use case and warns that the sketch remains open until a consuming operation closes it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/MCP_CAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server