Skip to main content
Glama

revolve

Turn a 2D sketch profile into a solid 3D shape by revolving it around an axis.

Instructions

Revolve a sketch profile around an axis to create a solid body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sketch_indexNoIndex of the sketch (0-based). Uses last sketch if not specified.
profile_indexNoIndex of the profile (0-based).
axisNoRevolution axis: 'X', 'Y', 'Z', or a sketch line index like 'line:0'.X
angleNoRevolution angle in degrees. Use 360 for full revolution.
operationNoBoolean operation: 'new_body', 'join', 'cut', 'intersect'.new_body
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It states 'create a solid body' but the operation parameter includes 'cut', 'intersect', and 'join', which are boolean operations that modify existing bodies. This omission is misleading.

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?

A single sentence succinctly states the purpose, front-loading the verb and resource. No redundant words.

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

Completeness2/5

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

The description is too brief for a tool with 5 parameters and no output schema. It does not explain return values, default behavior (e.g., using last sketch), or the nuances of boolean operations. Significant gaps remain.

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?

All 5 parameters have schema descriptions (100% coverage), so the description adds no extra meaning. The baseline of 3 is appropriate, as the schema adequately defines each parameter.

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 'Revolve' and the resources 'sketch profile around an axis to create a solid body', which effectively distinguishes it from sibling tools like extrude or sweep.

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?

No guidance is provided on when to use revolve versus alternatives such as extrude, sweep, or loft. There is no mention of prerequisites, recommended scenarios, or 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