Skip to main content
Glama

Add Thread

add_thread

Generate a solid ISO 60-degree helical thread with real cut geometry for external studs or internal taps. Replaces metadata-only thread flags with actual 3D solids for precise CAD assemblies.

Instructions

Generate a REAL helical ISO-style 60-degree thread as a static solid.

Unlike hole/list_thread_options (which only flag a thread as metadata), this cuts actual helical geometry: a truncated triangular rib swept along a helix and fused to a core cylinder.

All lengths in mm, angles in degrees. diameter: nominal MAJOR (crest) diameter, mm. For internal=True this is the bore the tap fits. pitch: thread pitch, mm per turn (e.g. M8 coarse = 1.25). length: threaded length along +Z from z=0, mm. internal: False (default) -> a finished externally-threaded stud. True -> a TAP/insert cutting-tool solid sized to the bore; fuse it into (or cut it from) a bored hole in your part to produce a threaded bore. starts: number of thread starts, >=1. Multi-start repeats the helix rotated by 360/starts and uses lead = pitch*starts. grade: optional material / property class as ordered ("8.8", "A2"). Changes no geometry; it completes the DIN 976-1 threaded-rod designation stamped on an EXTERNAL single-start thread — that solid is studding, a thing you buy by the metre. An internal thread is a tap-shaped cutting tool and a multi-start is not a stock item, so neither is designated at all. placement: optional [x, y, z] mm translation of the solid's base (default at the origin, axis along +Z). name: optional object name.

Geometry note: the modeled minor (root) uses the ISO 5H/8 truncation; the reported minor_diameter uses the standard ISO formula diameter - 1.0825*pitch. Fallback behaviour: if the helical sweep cannot produce a valid solid the tool returns a plain cylinder tagged with the thread spec and modeled=False (this is rare for sane M-series inputs); always check the modeled flag.

Returns {handle, name, volume (mm^3), major_diameter (mm), minor_diameter (mm), pitch (mm), length (mm), starts (int), internal (bool), modeled (bool), designation, orderable, catalog}. Studding is bought by the bar and cut, so any length up to the longest stock bar reads as stocked with a note that it is a cut. Mating numbers: drill/bore minor_diameter to tap an internal thread; clear a major_diameter (+clearance) hole to pass an external stud.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThread
gradeNo
pitchYes
lengthYes
startsNo
diameterYes
internalNo
placementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations carry almost no behavioral information, so the description carries the full burden. It discloses a fallback behavior (plain cylinder with modeled=False if the helical sweep fails), the exact geometric truncation rule, the grade designation logic for orderable studding, and the full return shape. This is far more than the annotations provide and is highly useful for predicting tool behavior.

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?

The description is long but well-organized: core purpose, sibling contrast, parameter details, geometry note, fallback, return values, and mating guidance. Nearly every sentence earns its place, though some sections (e.g., the grade/studding explanation) are more elaborate than strictly necessary. Overall it is dense but structured enough to remain navigable.

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

Completeness5/5

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

For a complex 8-parameter tool with no output schema, the description covers all bases: parameter semantics, geometry model, fallback behavior, return fields, and practical mating usage. An agent has enough information to decide whether to call this tool, set parameters correctly, and interpret the result without additional lookups.

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 0%, so the description must compensate, and it does comprehensively. Every parameter (diameter, pitch, length, internal, starts, grade, placement, name) is explained with units, defaults, semantic meaning (e.g., internal=True bore sizing), and special cases. The description adds meaning that the bare schema completely lacks.

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 opens with a specific verb and resource: 'Generate a REAL helical ISO-style 60-degree thread as a static solid.' It further distinguishes itself from siblings by explicitly contrasting with `hole`/`list_thread_options`, which only flag thread metadata. This leaves no ambiguity about what the tool does or how it differs from nearby alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names alternatives and the condition for choosing them: 'Unlike `hole`/`list_thread_options` (which only flag a thread as metadata), this cuts actual helical geometry.' It also gives clear internal/external usage guidance, multi-start behavior, and mating instructions for tapped bores and clearance holes, making when-to-use and when-not-to-use explicit.

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