Skip to main content
Glama
LGDiMaggio

Predictive Maintenance MCP Server

by LGDiMaggio

extract_manual_specs

Extract machine specifications including bearing designations, operating speeds, and power ratings from equipment manual PDFs.

Instructions

    Extract machine specifications from equipment manual PDF.

    Automatically extracts:
    - Bearing designations (e.g., SKF 6205, FAG NU2205)
    - Operating speeds (RPM values)
    - Power ratings (kW, HP, MW)
    - Text excerpt for LLM context

    Results are cached for fast repeated access.

    **IMPORTANT - LLM Usage Guidelines:**
    - This tool returns ONLY data extracted from the manual text
    - DO NOT add information not present in the extraction results
    - DO NOT make assumptions about missing specifications
    - If a specification is not in the results, tell the user it was not found
    - ALWAYS base your response exclusively on the returned dictionary
    - If user needs more detail, suggest using read_manual_excerpt() to read full text
    - DO NOT invent bearing geometries, frequencies, or other technical data

    **WORKFLOW for missing bearing geometry:**
    1. Check if bearing geometry is in extraction results (rare in manuals)
    2. If not found, use search_bearing_catalog(bearing_designation) tool
    3. If bearing not in catalog, ask user to provide:
       - All geometric parameters (num_balls, ball_diameter_mm, pitch_diameter_mm, contact_angle_deg)
       - OR upload manufacturer catalog to bearing_catalogs/ directory

    Args:
        manual_filename: PDF filename in resources/machine_manuals/
        use_cache: Use cached extraction if available (default: True)
        ctx: MCP context

    Returns:
        Dictionary with extracted specifications and text excerpt

    Example:
        >>> specs = extract_manual_specs("pump_XYZ_manual.pdf")
        >>> print(f"Bearings: {specs['bearings']}")
        >>> print(f"RPM: {specs['rpm_values']}")
        >>> print(f"Power: {specs['power_ratings']}")
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
manual_filenameYes
use_cacheNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, but the description discloses behavioral traits: results are cached for fast access, tool returns only extracted data, and it lists what is automatically extracted. It does not contradict any annotations.

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?

The description is structured with clear sections (extracted items, LLM guidelines, workflow, args, returns, example). It is somewhat lengthy due to necessary guidelines but every sentence adds value.

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 complexity and sibling tools (read_manual_excerpt, search_bearing_catalog), the description provides a complete decision framework, including when to use each sibling and how to handle missing data.

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 has 0% description coverage, but the description explains manual_filename as 'PDF filename in resources/machine_manuals/' and use_cache as 'Use cached extraction if available', adding meaning beyond the schema's titles.

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 extracts machine specifications from equipment manual PDFs and lists specific extracted items (bearings, speeds, power, text excerpt). It distinguishes from sibling tools by referencing read_manual_excerpt and search_bearing_catalog.

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?

Explicit 'LLM Usage Guidelines' section details when to use the tool, what not to do (e.g., do not add information not present), and provides a workflow for missing bearing geometry. It references alternatives like read_manual_excerpt and search_bearing_catalog.

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