Skip to main content
Glama

Add Pulley

add_pulley

Creates a static timing-belt or V-belt pulley solid from tooth count, belt pitch, and width, with optional flanges and placement for belt-drive assemblies.

Instructions

Add a timing-belt (or V) pulley as a static solid. Axis is +Z; toothed belt face spans z in [0, width].

teeth: tooth count (>= 6). belt_pitch: belt tooth pitch mm/tooth (e.g. 2.0 for GT2, 3.0 for GT3/HTD-3M); pitch diameter PD = belt_pitch * teeth / pi. width: belt-face length mm. flanged: True adds two thin guide discs (radius PD/2 + 2*belt_pitch) at each end to retain the belt. height: optional mm; OVERRIDES width when given (default height = width). placement: optional [x, y, z] mm translation of the axis base. name: object label.

Returns {handle, name, volume, pitch_diameter, belt_pitch, teeth, width, flanged}. pitch_diameter (mm) is the mating number: the centre distance to a mating pulley plus the required belt length derive from the two pitch diameters and the same belt_pitch.

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": {
      "teeth": "<teeth>",
      "belt_pitch": "<belt_pitch>",
      "width": "<width>"
    },
    "name": "add_pulley"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPulley
teethYes
widthYes
heightNo
flangedNo
placementNo
workspaceNoRun this call in this named workspace
belt_pitchYes

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.2/5.0
Behavior4/5

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

Annotations only declare this is a non-destructive, non-open-world creation tool, and the description adds real context beyond that: the +Z axis convention, the belt-face span, the constraint teeth >= 6, and the fact that height silently overrides width. It stops short of stating document/workspace prerequisites or failure modes, which matters for a mutation tool.

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?

Purpose comes first, parameters second, return contract last, and every clause carries information (formulas, defaults, override rules) rather than filler. It is dense but not padded; the cramped line breaks slightly hurt scanability.

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 eight parameters, 13% schema coverage and no output schema, the description does nearly all the work, including a full return list and an explanation that pitch_diameter is the mating number used for centre distance and belt length. The remaining gap is the workspace/precondition story, which an agent creating geometry would want.

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 13%, so the description must carry the load, and it does: teeth, belt_pitch (with concrete GT2/GT3 values and the PD formula), width, flanged guide-disc geometry, the height-overrides-width rule, and placement as an [x, y, z] translation of the axis base. Only workspace is left undocumented, and the schema covers that one.

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?

Opens with a specific verb and resource: "Add a timing-belt (or V) pulley as a static solid." This clearly separates it from geometric siblings such as add_gear, add_sprocket and add_rack, and the axis/orientation note anchors what is actually produced.

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 belt_pitch examples (GT2 = 2.0, GT3/HTD-3M = 3.0) imply when the tool applies, but there is no explicit statement of when to choose it over add_sprocket or when to use belt_drive for the mating calculation. Usage has to be inferred from domain knowledge.

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