Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

search_bearing_catalog

Retrieve verified bearing specifications and geometry from a local catalog. Provides results or suggestions when a bearing is not listed.

Instructions

    Search for bearing specifications in the local verified catalog.

    Fallback for when the machine manual names a bearing but not its
    geometry. The catalog is small BY DESIGN: only entries whose
    geometry is traceable to a public source (mandatory `source`
    citation). A miss is a legitimate negative outcome — ask the user
    for the geometry; never guess it.

    Args:
        bearing_id: Bearing designation (e.g. "6205", "SKF 6205-2RS")
        ctx: MCP context

    Returns:
        Dictionary with bearing specifications if found, or a
        BearingCatalogMiss (status='not_found', suggestion,
        catalog_contains) when the bearing is not in the catalog.

    Raises:
        Exception: If the catalog itself cannot be read (missing or
            malformed common_bearings_catalog.json).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bearing_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses key behaviors: catalog is small, entries require public source, miss is legitimate, returns BearingCatalogMiss on failure, raises exception if catalog file is corrupted. No annotations exist, so description carries full burden and excels.

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?

Well-structured with sections for purpose, usage, args, returns, and exceptions. Slightly verbose but every sentence adds value. Front-loaded with core purpose.

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?

Complete for a single-parameter tool with an output schema. Explains failure modes, catalog constraints, and exception handling. No gaps given the tool's simplicity.

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?

The only parameter 'bearing_id' is described with examples ('6205', 'SKF 6205-2RS') and its role as a bearing designation. This adds significant meaning beyond the schema's type and title.

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 clearly states 'Search for bearing specifications in the local verified catalog' with a specific verb and resource. It distinguishes from sibling tools by focusing on catalog searching, not analysis or diagnosis.

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?

Explicitly states it is a 'fallback for when the machine manual names a bearing but not its geometry.' Provides guidance on how to handle a miss: 'ask the user for the geometry; never guess it.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LGDiMaggio/predictive-maintenance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server