Skip to main content
Glama

Loft

loft

Creates additive geometry by connecting two or more ordered sketches, with options to close the loop or use ruled surfaces between sections.

Instructions

Loft (additively) between two or more sketches.

sketches: ordered list of sketch handles. The first becomes the Profile, the rest become Sections. closed: True connects the last section back to the first (toroidal). ruled: True uses straight ruled surfaces between adjacent sections.

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": {
      "sketches": "<sketches>"
    },
    "name": "loft"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLoft
ruledNo
closedNo
reversedNo
sketchesYes
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

B3.3/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 description does not need to restate safety. It usefully adds that the operation is additive and explains the closed (toroidal) and ruled surface behaviors, but it is silent on failure conditions, whether a new body/feature is created, and how existing geometry is affected.

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 purpose is front-loaded, then the three key semantics are delivered in tight lines with no filler. Every sentence and clause carries information relevant to invoking the tool.

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 six-parameter geometry creation tool with no output schema and sparse schema descriptions, the description covers the most important inputs but not the full surface. It omits reversed, name, and workspace behavior, and does not describe the resulting feature or common failure modes.

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

Parameters3/5

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

Schema description coverage is only 17%, and the description compensates partially: it explains that sketches is an ordered list where the first is the Profile and the rest are Sections, and it explains closed and ruled. However, it leaves reversed completely undocumented and says nothing about name, while workspace is covered only by the schema.

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 states a specific verb and resource: 'Loft ... between two or more sketches', with an additive qualifier. This is clear for a CAD-literate agent, but it does not contrast the operation with sibling shape-creation tools such as pad, sweep, or revolve.

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?

The description never says when to choose lofting over sweep, revolve, or pad, nor does it state prerequisites or exclusions. The only implied guidance is the 'two or more sketches' minimum, which is inherent in the operation rather than an explicit usage rule.

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