Skip to main content
Glama

loft

Create a surface or solid body by transitioning between multiple sketch profiles. Use guide rails to control shape, a center line to constrain the path, or close the loft.

Instructions

Create a loft between two or more sketch profiles. Optionally use guide rails to control the surface transition, a center line to constrain the loft, or create a closed loft.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profilesYesArray of {sketch_index, profile_index} objects defining loft sections.
guide_railsNoOptional array of {sketch_index, curve_index} for guide rails controlling the surface shape.
center_lineNoOptional center line: {sketch_index, curve_index} to constrain the loft path.
is_closedNoIf true, create a closed loft (last section connects back to first).
operationNoBoolean operation: 'new_body', 'join', 'cut', 'intersect'.new_body
Behavior2/5

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

No annotations are provided, so the description carries full burden. It describes what the tool does but omits behavioral traits such as modifiability to the design, prerequisites (e.g., parallel sketches), or side effects. The schema covers parameter details, but the description adds minimal behavioral insight.

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 a single concise sentence that front-loads the main action and each clause adds value. No redundant or wasted words.

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?

The tool has 5 parameters with nested objects and no output schema. The description covers the core concept but lacks prerequisites (e.g., sketches exist, parallel planes) and does not specify what the tool returns. Adequate but not fully complete.

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 coverage is 100% with descriptions for all parameters. The description adds context by mentioning 'two or more sketch profiles' and optional features, but does not significantly enhance meaning beyond what the schema already provides.

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 'Create' and the resource 'a loft between two or more sketch profiles', and distinguishes from sibling tools like sweep and extrude by specifying the use of multiple profiles.

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 description lists optional features (guide rails, center line, closed loft) but does not provide explicit guidance on when to use this tool versus alternatives like sweep or extrude, nor does it mention when not to use 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/mikan-atomoki/text-to-model'

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