Bearing Product Search

What problem it solves

When selecting or sourcing bearings, engineers often need to check whether a part number exists, which brand it belongs to, and whether the inner and outer diameters fit a given envelope. Searching catalogs or asking suppliers one item at a time can miss constraints, and empty results can leave it unclear which filter should be relaxed. This skill turns that lookup into a structured database query, making it easier to narrow a vague requirement down to candidate part numbers.

How the skill works

It queries a bearing product database using fields such as keyword, partNumber, minInnerDiameter, maxInnerDiameter, minOuterDiameter, maxOuterDiameter, brandId, and bearingTypeId, with page and pageSize for pagination. All filters are optional, and the default page size is 20 records. The workflow is:
- Parse input: extract model, brand, diameter ranges, and bearing type from the request.
- Search the database: use GET /api/bearings/search for list queries and GET /api/bearings/by-part/:partNumber for exact part lookup, which reduces keyword ambiguity.
- Support context: call GET /api/brands, GET /api/bearing-types, or GET /api/bearings/hot to enrich results with brands, types, or recommendations.
- Format output: present results as a table or list, and suggest adjustments when the result set is empty.

Boundaries and notes

This is useful for product lookup, part-number validation, and preliminary selection filtering. It should not replace final engineering validation or life calculations. Results depend on the database coverage; if a series, batch, or replacement item is missing, the search may be incomplete. Diameter values are assumed to be in mm, and brand/type filters require accurate brandId and bearingTypeId values.