Skip to main content
Glama

Revolve

revolve

Rotates a sketch around a body origin axis (X, Y, or Z) by a specified angle to create a 3D feature.

Instructions

Revolve a sketch around a body origin axis ('X'|'Y'|'Z') by angle deg.

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": {
      "sketch": "<sketch>"
    },
    "name": "revolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNoY
nameNoRevolution
angleNo
sketchYes
reversedNo
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.1/5.0
Behavior3/5

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

Annotations already declare it is a non-destructive, non-open-world write operation, lowering the disclosure bar. The description adds the useful constraints that the axis is a body origin axis and that the angle is in degrees, but says nothing about whether a new body/feature is created, what happens with angles > 360, or effects on the source sketch.

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?

A single front-loaded sentence with no filler; the axis domain and angle unit are packed in efficiently. Brevity is the only structural weakness, but nothing in the sentence is wasted.

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?

For a 6-parameter modeling mutation with no output schema and 17% schema coverage, one sentence leaves major gaps: the required sketch reference, the meaning of `reversed`, the default 360° behavior, and what the call returns (feature name/body) are all unaddressed.

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%, so the description must compensate; it does partially by giving the axis value domain ('X'|'Y'|'Z', which the schema lacks as an enum) and the degree unit for angle. However, the required `sketch` parameter, `reversed`, and `name` remain undocumented anywhere.

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?

A specific verb plus resource ('Revolve a sketch') with the sweep axis and angle named, which separates it from pad/loft/sweep siblings by operation type. It stops short of explicitly naming those siblings or stating what the result is (a solid feature on a body).

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 when-to-use or when-not-to-use guidance and no prerequisites (e.g. that the sketch must exist and be closed). The large family of alternative solid-creation tools (pad, sweep, loft, helix) is never referenced, so the agent must infer selection rules.

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