Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

calculate_bearing_characteristic_frequencies

Compute bearing fault frequencies (BPFO, BPFI, BSF, FTF) from bearing geometry and shaft speed to diagnose machine faults.

Instructions

    Calculate bearing characteristic frequencies from geometry.

    Uses formulas from ISO 15243:2017 and SKF bearing handbook.
    Essential for bearing fault diagnosis when you know bearing geometry
    but don't have pre-calculated frequencies.

    **IMPORTANT - LLM Usage Guidelines:**
    - This tool REQUIRES exact bearing geometry parameters
    - DO NOT guess or estimate bearing geometry if not provided
    - DO NOT use "typical" or "standard" values without user confirmation
    - If geometry is unknown, tell user to:
      1. Check manual using read_manual_excerpt()
      2. Look up bearing in manufacturer catalog (e.g., SKF, FAG, NSK)
      3. Use lookup_bearing_in_catalog() if bearing designation is known
      4. Measure the bearing physically if necessary
    - ONLY calculate with geometry explicitly provided by user or found in manual
    - DO NOT make assumptions about contact angle (use 0 deg if unknown and inform user)

    Args:
        num_balls: Number of rolling elements (Z)
        ball_diameter_mm: Ball/roller diameter (Bd) in mm
        pitch_diameter_mm: Pitch circle diameter (Pd) in mm
        contact_angle_deg: Contact angle (alpha) in degrees (0 deg for deep groove ball bearings)
        shaft_speed_rpm: Shaft rotation speed in RPM
        ctx: MCP context

    Returns:
        Dictionary with BPFO, BPFI, BSF, FTF in Hz

    Example:
        >>> # For SKF 6205 bearing at 1797 RPM
        >>> freqs = calculate_bearing_characteristic_frequencies(
        ...     num_balls=9,
        ...     ball_diameter_mm=7.94,
        ...     pitch_diameter_mm=34.55,
        ...     contact_angle_deg=0.0,
        ...     shaft_speed_rpm=1797
        ... )
        >>> print(f"BPFO: {freqs['BPFO']:.2f} Hz")
        BPFO: 81.13 Hz

    Common bearing geometries:
    - Deep groove ball bearings: contact_angle = 0 deg
    - Angular contact bearings: contact_angle = 15-40 deg
    - Cylindrical roller bearings: contact_angle = 0 deg
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
num_ballsYes
ball_diameter_mmYes
pitch_diameter_mmYes
contact_angle_degNo
shaft_speed_rpmNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully carries the burden of behavioral transparency. It discloses that it uses standards (ISO 15243:2017 and SKF handbook), explains the input parameters and their meanings, and states the return format (dictionary with BPFO, BPFI, BSF, FTF in Hz). It also provides an example with output. No destructive behavior is relevant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured, starting with the purpose, then a clearly labeled usage guidelines section, then Args, Returns, Example, and Common geometries. Every sentence adds value; there is no fluff. It is appropriately sized for the complexity of the tool.

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?

Given the tool's moderate complexity (5 parameters, 3 required, no enums, no nested objects), the description is thorough. It covers all necessary aspects: purpose, usage constraints, parameter explanations, return format, and an example. The output schema is implicitly described by listing the dictionary keys and units.

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 0%, so the description must compensate. It does so by explaining each parameter in the Args section with symbolic names (Z, Bd, Pd) and units, and by providing common values for contact angle. This adds significant meaning beyond the schema's bare titles and defaults.

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 the tool's purpose: 'Calculate bearing characteristic frequencies from geometry.' It specifies the verb 'calculate,' the resource 'bearing characteristic frequencies,' and the context 'from geometry.' It distinguishes from sibling tools like 'lookup_bearing_and_compute_tool' by emphasizing that it computes from exact geometry rather than looking up pre-calculated values.

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?

The description provides extensive usage guidelines in a dedicated section, including when to use (knowing exact geometry), when not to use (guessing), and explicit alternatives (read_manual_excerpt, lookup_bearing_in_catalog). It warns against assumptions and states that user confirmation is required before using typical values. This is exceptional guidance.

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