Skip to main content
Glama

Helix

helix

Creates a 1D helical curve from radius, pitch, height, and cone angle; use it as a sweep spine to form 3D threaded or coiled solids.

Instructions

Generate a Part::Helix curve. radius, pitch, height in mm. angle (deg) is the cone angle (0 = cylindrical helix, >0 = conical).

Returns a handle to a 1D helical curve. To get a 3D helical solid (e.g. for threads), use the curve as the spine of a sweep.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "helix"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoHelix
angleNo
pitchNo
heightNo
radiusNo
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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: it returns a handle (important since there is no output schema) and that the result is a 1D curve requiring a downstream sweep to become a solid. It does not mention whether an active document or open transaction is required, which is a remaining gap for a non-read-only tool.

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?

Three short sentences, front-loaded with the action, then parameter semantics, then usage guidance. No filler, and the most decision-relevant fact (curve vs solid) is not buried.

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?

With no output schema, the description correctly fills the return-value gap by describing the handle to a 1D curve. For a 6-parameter geometry constructor it is mostly complete, but it omits preconditions such as needing an active document/workspace before generation.

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

Parameters5/5

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

Schema description coverage is only 17% (just workspace), so the description carries the burden and does so well: it gives units for radius, pitch and height (mm) and, critically, explains that angle is a cone angle in degrees where 0 = cylindrical and >0 = conical. That is exactly the non-obvious semantic an agent could not infer from a bare number field.

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?

States a specific verb and resource ('Generate a Part::Helix curve') and immediately defines the scope: a 1D helical curve, not a solid. The closing sentence distinguishes it from solid-producing workflows (sweep), so an agent can tell what it will and will not produce without inspecting any schema.

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?

Explicitly says to use the output as a spine for a sweep when a 3D helical solid (e.g. threads) is wanted, which gives clear composition guidance and names the alternative path. It does not address siblings like add_thread or list_thread_options, which could also be the right choice for thread features, so the routing is not fully exhaustive.

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