Skip to main content
Glama

Engrave Text

engrave_text

Engrave or emboss extruded text on a planar solid face, centered on the face centroid, to add labels, part numbers, or markings directly to a 3D model.

Instructions

Engrave (cut) or emboss (add) extruded text on a planar face of a solid, centred on the face centroid. The host is replaced by the returned handle.

face: planar face — f_* tag (preferred), 'FaceN', or int. size: cap height mm. depth: engrave/emboss depth mm. mode: 'engrave' (removes material) | 'emboss' (adds). position: optional [u, v] mm offset from the centroid along the text's X/Y. font: absolute path to a .ttf/.ttc. Omitted: only macOS Arial/Helvetica are probed, so elsewhere it raises — pass a path.

Returns {handle, name, volume (mm^3 of the result), text, mode, depth}.

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": {
      "handle": "<handle>",
      "face": "<face>",
      "text": "<text>"
    },
    "name": "engrave_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
faceYes
fontNo
modeNoengrave
nameNoText
sizeNo
textYes
depthNo
handleYes
positionNo
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.4/5.0
Behavior4/5

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

The description adds substantive behavior beyond the annotations: the host is replaced by the returned handle, engraving removes material while embossing adds it, placement is centered on the face centroid, and font omission can raise on non-macOS. The annotations already cover the safety profile, so this is strong supplemental disclosure.

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?

The description is compact and front-loaded with the operation, followed by tightly scoped parameter notes and a return-value summary. Every line provides actionable information.

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 and very low schema description coverage, the description gives the essential context: operation semantics, placement, return shape, and font failure behavior. Minor gaps remain around the optional name and workspace parameters, but the tool is callable correctly from this description.

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 description coverage is only 10%, so the description carries most of the burden and does so well for the key parameters: face tag formats, size/depth units in mm, mode values, position offset semantics, and font path requirements. It leaves name, handle input, and workspace unexplained, but the core modeling parameters are well covered.

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 states a specific verb (engrave/emboss), the resource (extruded text on a planar face), and the scope (centred on the face centroid). It is immediately distinguishable from drawing-annotation and sketch tools in the sibling list.

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?

It clearly establishes the operation context and explains the two modes, plus an important fallback caveat: if font is omitted, only macOS Arial/Helvetica are probed and it raises elsewhere. It does not explicitly compare against alternatives, but no sibling appears to perform the same solid-text operation.

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