Skip to main content
Glama

Add Sprocket

add_sprocket

Creates a static solid-plate ISO 606/ANSI roller-chain sprocket from tooth count, chain pitch, and roller diameter for fit checks and visualisation.

Instructions

Add a roller-chain sprocket (ISO 606 / ANSI), built as a static solid plate.

teeth: tooth count (>= 3). chain_pitch: chain link pitch in mm (e.g. 12.7 for #40 / ANSI 40 chain). roller_diameter: chain roller diameter in mm. height: plate thickness in mm (default 6.0). placement: optional [x, y, z] mm translation.

Build: a disc of tip radius ~= pitch_radius + chain_pitch*0.3 with teeth roller seats (circular pockets, radius roller_diameter/2 * 1.05) cut on the pitch circle, one per tooth. This is a fit/visualisation approximation of the true ISO 606 tooth form, not a load-rated profile.

Returns {handle, name, volume, pitch_diameter, chain_pitch, teeth, tip_radius, bore}. pitch_diameter (mm) = chain_pitch / sin(pi/teeth) and chain_pitch are the MATING numbers: a chain of the same chain_pitch wraps the sprocket, and the centre distance between two sprockets derives from their pitch_diameters. bore is 0 (no shaft hole cut yet — drill one with the hole command).

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>",
      "chain_pitch": "<chain_pitch>",
      "roller_diameter": "<roller_diameter>"
    },
    "name": "add_sprocket"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSprocket
teethYes
heightNo
placementNo
workspaceNoRun this call in this named workspace
chain_pitchYes
roller_diameterYes

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.6/5.0
Behavior5/5

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

Annotations only declare the generic non-read-only/non-destructive profile; the description goes well beyond by disclosing the exact geometric construction algorithm (tip radius, seat radius multiplier), the accuracy caveat, and that bore is 0 so no shaft hole exists yet. It also documents the returned fields and the engineering meaning of the mating numbers, which annotations cannot convey.

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?

Front-loaded with purpose, then parameters, then construction, then return values — a sensible order and no filler sentences. The build-algorithm paragraph is slightly longer than an agent strictly needs but each clause conveys real geometry information.

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?

With no output schema, the description fully documents the return object (handle, name, volume, pitch_diameter, chain_pitch, teeth, tip_radius, bore) and explains how pitch_diameter relates to real chain mating and centre distance. It also flags the immediate follow-up action needed (drill the bore), so nothing required for correct use is missing.

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

Parameters4/5

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

Schema coverage is only 14%, so the description carries most of the load: it gives units (mm) and a concrete example (12.7 for #40 / ANSI 40 chain), the constraint teeth >= 3, the height default of 6.0, and the [x, y, z] mm meaning of placement. Only the `name` parameter is left unaddressed, which is minor and self-evident.

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?

First sentence names a specific verb and resource ('Add a roller-chain sprocket (ISO 606 / ANSI)') plus the construction form ('static solid plate'), which cleanly separates it from siblings like add_gear, add_pulley and add_rack. An agent can select it without opening the 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?

States the important boundary condition — it is a fit/visualisation approximation, not a load-rated profile — which tells the agent when not to rely on it for strength work, and routes the agent to the `hole` command for a bore. It does not, however, compare itself to add_gear/add_pulley alternatives for power transmission; that is inferred from the naming only.

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