Skip to main content
Glama

Add Bearing

add_bearing

Creates an annular deep-groove ball-bearing envelope solid from a designation or bore, OD, and width to size shafts, housing bores, and shoulder spacing.

Instructions

Add a deep-groove ball bearing as an assembly envelope solid: an annular ring (outer-diameter cylinder minus bore cylinder) of the given width, axis along +Z. Balls/races are not modeled — this is the fit envelope a coordinator needs to size the shaft, the housing bore, and the shoulder spacing.

Specify dimensions ONE of two ways:

  • designation: a standard metric series code, looked up in a built-in table. Known: "608", "623", "624", "625", "626", "688", "6000", "6200", "6800", "6900". (e.g. "608" -> bore 8, OD 22, width 7 mm.)

  • bore + outer_diameter + width: explicit dims in mm (all three required). Explicit values override a designation's table values when both are given.

bore: inner-bore diameter mm (sizes the shaft). outer_diameter: OD mm (sizes the housing bore). width: axial length mm (shoulder spacing). placement: optional [x, y, z] mm translation of the bearing's near face.

seals: open (default) | RS | 2RS | RZ | 2RZ | Z | 2Z. It changes no geometry — the envelope is identical — but it IS part of the orderable identity: 608, 608-2Z and 608-2RS are three different purchases with different drag, speed limits and prices. It is folded into the canonical designation stamped on the part ("608-2RS").

A bearing built from raw bore/OD/width with NO designation is a dimensional envelope, not a purchasable part, and is deliberately left undesignated rather than given a made-up catalog number.

Raises ValueError if the designation is unknown and dims are incomplete, or if outer_diameter <= bore.

Returns {handle, name, designation, bore, outer_diameter, width, volume, orderable, catalog}. handle starts "bearing_". designation is None when built from explicit dims; orderable is the designation card, whose own designation carries the seal suffix; catalog is the off-the-shelf verdict (stocked or not, None for an undesignated envelope).

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": "add_bearing"
  }
}

Input Schema

NameRequiredDescriptionDefault
boreNo
nameNoBearing
sealsNoopen
widthNo
placementNo
workspaceNoRun this call in this named workspace
designationNo
outer_diameterNo

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

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

Beyond the annotations (non-read-only, non-destructive), it discloses that seals change no geometry but do change orderable identity, that undesignated envelopes are deliberately not given catalog numbers, the exact ValueError conditions (unknown designation with incomplete dims, OD <= bore), and the shape of the returned handle/name/designation/volume/orderable/catalog fields.

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 the purpose, then structured as input modes, parameter glossary, seals caveat, errors, and returns. It is long (~250 words) and the seals and 'deliberately left undesignated' passages repeat the same orderable-vs-envelope idea, which could be tightened, but almost every sentence carries real 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?

There is no output schema and only 0 required params, so the description must explain both input and output; it does both, including the canonical return keys, handle prefix, and how `orderable` and `catalog` differ. An agent has everything needed to call this correctly on the first try.

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 coverage is only 13% (just `workspace`), so the description carries the load and does so: it defines units (mm) and physical meaning for bore, outer_diameter, width and placement, enumerates the seals values that the schema leaves as a bare string (open | RS | 2RS | RZ | 2RZ | Z | 2Z), and explains designation lookup and override precedence.

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?

Specific verb + resource (add a deep-groove ball bearing as an annular envelope solid) with an explicit statement of what is and is not modeled ('Balls/races are not modeled — this is the fit envelope'). This immediately distinguishes it from sibling constructors like add_gear, add_sprocket, and add_primitive.

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?

It sets the use context clearly (sizing shaft, housing bore, shoulder spacing for a coordinator) and gives explicit rules for the two input modes, including that explicit dims override designation table values. It never names an alternative sibling tool (e.g. catalog_search or standard_part_designate) or states when not to use it, so it stops short of a 5.

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